Versions Compared

Old Version 1

changes.mady.by.user Bruno Conde

Saved on

compared with

New Version Current

changes.mady.by.user user-0caa0

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The options available in General Settings are:

Table of Contents


Note

A JIRA Jira re-index operation is recommended when there are changes to Issue Type Mappings.

...

Sub-Requirements

In this section, you can define how Requirements and Sub-Requirements are associated. If the JIRA Jira link mechanism is used, then the "Issue Link Type" must be chosen as well as the direction from the parent requirement to the child requirement. If " Sub-Task"s Tasks are used, then simply check the "Use Sub-Tasks Issues" option. Note: The Sub-Task requirement issue types must also be associated with "Requirements" in the Issue Type Mapping section. 

...

When this option is enabled, Sub-Requirements are associated with Requirements by Sub-Task Issues. When this option is disabled, Sub-Requirements are associated with Requirements with issue links configured bellowbelow.

Use Epic - Story relation

When this option is enabled, Story issues are associated with Epic issues as Sub-requirementsRequirements.

Issue Link Type

If Sub-Requirements are not defined as sub-tasks, you can configure a JIRA Jira link to define this association. Select the issue link type for the Requirement - Sub-Requirement relationrelationship.

Direction

Select the Link Direction for the parent > child relation relationship of the Requirement > Sub-Requirement. 

 



Info

For more information on Requirement Status and coverage calculation please see , please refer to the Requirements Coverage Analysis.