Creating new requirements from existing requirements
You may be able to create new requirements from existing requirements depending on how your team uses Helix ALM. For example, you may be able to create functional requirements from business requirements. Information from the source requirement is copied to the new requirement depending on the project configuration.
Tip: You can also duplicate requirements. When duplicating, you can control the information copied to the new requirement, such as history and file attachments. The type for the new requirement is the same as the source requirement and cannot be changed. See Duplicating requirements. When you create new requirement from existing requirements, the information copied to the new requirement is already configured, but you can update it when you create the requirement. Only field information is copied, not historical information, such as workflow, emails, and attachments.
1. Click Actions and choose Add Related Requirement when you are viewing or editing a requirement. If you can create multiple requirement types, choose a type. You can also select a requirement in the Requirements list or in a document to create a new requirement from it.
Note: If you are required to select a document to add the new requirement to, the Select Requirement Document dialog box opens. To find a document, you can search, apply a filter, or view a list of recently accessed documents. Select the document and click Select.
The Add
2. Make any changes.
3. Save the requirement.
- Click Save to save and return to the Requirements list.
- Click Save and Add Another to save and add another requirement.
Tip: Click Apply to save and continue working on the requirement.
You may be prompted to link the requirements. Click Add Link to create a link or Do Not Link if you do not want to create a link. See Working with related items.
The requirement is saved and added to the project. If the requirement was added to a document, the document opens and the requirement is selected.
