Issue artifacts for tests and requirements using R4J and T4J

Paul Newton October 18, 2018

I am just starting an agile software project where we intend to us R4J for requirements management and T4J for test management.

I can add issues to the tree views in the respective Requirements and Test tree views.  My question is about what kind of issues should populate those views.  Should I be using the extant issue types, either "story" or "bug" to represent individual requirements and tests?  Should I be using appropriate customized issue types? If customized, would I customize my own types or is there a source for prefabricated Requirement and Test issue types?

 

Thanks for any help.

Paul N.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events