User Guide | 2019.2

Editing requirements

Edit a requirement to add additional information or make changes based on review comments or changes to related items. If the current requirement version is shared in multiple requirement documents, all instances of the requirement are updated.

Tip:  If you need to update field values for multiple requirements, use bulk field changes. This allows you to quickly update multiple items simultaneously. See Updating Multiple Items.

1. In the Requirements list window, select the requirement and click Edit. You can also choose Edit > Edit.

You can also edit requirements directly in a document. See Editing requirements directly in documents.

The Edit Requirement dialog box opens.

Note:  Icons may indicate the item is locked or marked as suspect. See About item status indicators.

2. Make any changes to the general fields or description in the top part of the Edit Requirement dialog box.

3. Make any changes to information on the tabs in the dialog box.

Tab Displays: More information
Detail Custom field values used in the project. These are unique fields your team uses to capture additional information. Adding requirements
Workflow Work performed on the requirement as it moves through the workflow. Viewing workflow event history
Versions Historical versions of the requirement included in document snapshots captured at project milestones or specific points in time. Viewing historical requirement versions
Documents Documents the requirement is included in. Viewing documents that requirements are included in
Traceability Items linked to the requirement, relationships with other requirements, and options to perform impact analysis. You can add, edit, and delete links, mark linked items as suspect to indicate they may be impacted by changes, and investigate suspect dependencies. Working with item links and Performing impact analysis
Files Files attached to the requirement, including files attached from source control applications, such as Surround SCM. Viewing and downloading file attachments and Viewing local copies of source files
Email Email sent about the requirement. You can reply to email. Available only if email tracking is enabled for the project. Viewing email and Replying to email
Folders Folders the requirement is included in. You can add the requirement to other folders, move it to different folders, or remove it from folders. You cannot add or move the requirement to public folders you do not have permission to modify or are locked, or locked private folders. You cannot remove the requirement from locked folders. Organizing Items with Folders
History Historical information about the requirement, such as when it was created, when it was last modified, and all actions performed on it. Viewing Item History

Note:  To change the requirement type, see Changing requirement types.

4. Click Create Requirement to add a requirement based on the requirement. The button name may be different depending on the requirement types you can create. If you can create multiple requirement types, choose a type. See Creating new requirements from existing requirements.

5. Click Generate Test Case to create a test case based on the requirement. See Generating test cases from requirements.

6. Click Create Issue to add an issue based on the requirement. See Creating issues from requirements.

7. Click Send Email to email users about the requirement. See Emailing from Helix ALM.

8. Click Watch to be notified every time the requirement changes. See Watching issues to be notified about changes.

9. Save the requirement.

  • Click OK to save and close the requirement.
  • Click Apply to save and continue working on the requirement.

Tip:  If the changes impact linked or related items, you may want to mark the items as suspect. This flags the items to indicate they should be reviewed. See Marking items as suspect.