Edit requirement type mapping (ALM synchronization only)

When you create a link, you can map one or more ALM requirement types to each of the ALM Octane types: user story, feature. You can map one ALM requirement type to ALM Octane epics.

On the link configuration page, expand the nodes in the navigation tree and select the requirement link you want to edit. How do I get to the Link Configuration page?

Click Edit Link to enable changes, and Save Link to save your changes.

Requirement link nodes contain sub nodes for each mapped ALM requirement type. Each sub node displays the names of the mapped ALM Octane - ALM requirement types. If multiple requirement types are mapped to features or user stories, one type is used as the default. (Expand the pane to view the full names.)

  • The hierarchy of the mapped types in the ALM requirement tree must match the Epic > Feature > User Story hierarchy in ALM Octane. For details, see In ALM, prepare requirement types to match ALM Octane's (requirement synchronization).

    For requirement types mapped to epics or user stories, you can instruct Synchronizer to ignore a requirement's hierarchy when it does not match. Such requirements are then synchronized directly to the root of the ALM Octane backlog tree: Select Synchronize epics and user stories to the Backlog root. This option is located in the requirement link's General tab.

  • You must always run an integrity check after modifying a link's configuration. We also recommend running a simulation to prevent errors occurring in the actual synchronization. For details, see Step 6: Run synchronizations.

What do you want to do?

Remove a mapped requirement type

Right-click the sub node for the requirement type and select Remove Requirement Type.

Available only before you run the first successful synchronization for the link.

Map an additional requirement type

Right-click the node for the requirement link and select Add Requirement Type.

You can map additional requirement types to user stories and features. You can map a requirement type to epics, if they are not already mapped.

See also: