You are here:

Creating requirements from issues

If you work with requirements in Helix ALM, you can create requirements from issues. For example, you may create a requirement from a feature request to implement in an upcoming release. The issue information is copied to the requirement so users can review the issue details when defining additional requirement details.

1. Click Create Requirement when you are viewing or editing an issue.

The Select Requirement Type dialog box opens.

2. Select a requirement type and click OK.

The Add Requirement dialog box opens. Requirement information is added to the following fields by default:

Summary—Includes the issue number and summary.
Description—Includes the description from each issue Reported by record.
Detail tab—Issue custom field values. Only copied to the requirement if a requirement custom field with the same field name and type as issues exists.
Files tab—Includes file and source control attachments.

Note: Depending on project configuration, additional information may be copied from the issue. See Configuring item mapping rules.

3. Make any changes.

4. Click Add to save the requirement and add it to the project.

You can also click Apply to save the requirement and continue working on it. Click OK when you finish.

You may be prompted to link the requirement with the related issue. 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.

Tip: Depending on user options, the Add Requirement dialog box may remain open after the requirement is added. Click Cancel to close it. You can change the Add Multiple Requirements user option to automatically close the dialog box after adding a new requirement. See Setting add multiple items options.