You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Understanding Requirements and Defects

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.



Basic terms


Xray can re-use your existing issue types and consider them as Requirements & Defects. You don't need to create extra issue types!


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: 





What issue types can be used as Requirements?

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. 



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














  • No labels