Versions Compared

Old Version 4

changes.mady.by.user Sofia Canario

Saved on

compared with

New Version 5

changes.mady.by.user Sofia Canario

Saved on

Key

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

Requirements can be covered by Tests, and are the expected result for the system. 

Defects are identified during Tests Executions, and represent a condition in the system that does not meet the requirement or end-user expectations. 

In Jira, Requirements and Defects are going to be created as issues inside a project.


Gliffy Diagram
size600
nameBasic terms
pagePin3


UI Steps
UI Step

Decide which issue types to use


Tip

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

Tip
UI Step

Map Requirements & Defects


  1. 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".

Image Added

2. Click "Save"


UI Step

Confirm Sub-Requirements behaviour

By default Xray will have the following settings enabled: 


Image Added

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 "Requirement" & "Sub-Requirements"
  • Epic > Story 

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!

For example, your team can prefer to have issue types "Requirement" and "Defect".

Nevertheless, remember that can re-use existing issue types and you don't need to create extra ones!