Discuss with your team which issue types can be considered as Requirements & Defects. If none of the existing issues types is suitable, you can always create new ones!
Nevertheless, remember that 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 in JIRA, but the most common ones are:
Image Modified
Image Modified
Image Modified
Image Modified
What issue types can be used as Defects?
As within requirements, any issue type can be considered a defect.
By just using default JIRA issue types, the "Bug" is the strongest candidate to be mapped as a Defect.
Image Modified
UI Step
Map Requirements & Defects
In Jira's administration, in the Manage Apps tab, go to Issue Type Mapping and drag-and-drop the issue types that should be considered "requirements" and "defects".
2. Click "Save"
UI Step
Confirm Sub-Requirements behaviour
By default Xray will have the following settings enabled:
This means that a requirement can be associated with sub-requirements, resulting in a hierarchy of 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
If you decide to disable these options, you can set the sub-requirement behaviour using the JIRA linking mechanism. You just need to select which "Issue Link Type" to use and the correct "Direction.
Image Added
Warning
In order 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.
