Discuss with your team which issue types can be considered you will consider as Requirements & Defects. If none of the existing issues types is are suitable, you can always create new ones!
Nevertheless, remember that you can re-use existing issue types and you don't need to create extra ones!.
What issues type can be used as Requirements?
Basically, any issue type can be mapped as a requirement Requirement in JIRAJira, but the most common ones are:
What issue types can be used as Defects?
As within requirementswith Requirements, any issue type can be considered a defectDefect.
The most common to use is the "Bug" issue type , that is available by default when you install JIRA Jira Software.
UI Step
Map Requirements & Defects
Go to Jira Administration > Manage Apps > Xray > Issue Type Mapping and drag-and-drop the issue types that should be considered "requirementsRequirements" and "defectsDefects.".
2. Click "Save"
UI Step
Confirm Sub-Requirements behaviour
By default Xray will have the following settings enabled:
This means that a requirement Requirement can be associated with subSub-requirementsRequirements, resulting in a hierarchy of requirement Requirement issues. With these options enabled, you will have this behaviour by just using the relation:
Issue > Sub-Task - For example using issue types like "Requirement" & "Sub-Requirements"
Epic > Story
Note
In order to To have "Sub-Tasks / Links" working correctly, you need to have the Sub-Task requirement issue types also be associated with "Requirements" in the "Issue Type Mapping" section. . For example, you can create a new issue type Sub-Requirement / Sub-Story and mapped as a Requirement.
If you decide to disable these options, you can set the sub-requirement behaviour using the JIRA Jira linking mechanism. You just need to select which "Issue Link Type" to use and the correct "Direction.
Note
A Jira re-index operation is recommended when there are changes to Issue Type Mappings.
