Is there any option to have Acceptance criteria as a separate entity like Story,bug etc

[Kanishk Azad]

Hi Team,

Can we have Acceptance criteria as a separate entity like Story,bug etc

Use Case :

Just like when we create a defect and link that defect to a story and this linkage is then visible in both that defect as well as that linked story when we search in Jira.

Similarly, if we want to map an "Acceptance Criteria" of a Story to a defect(and not whole story to defect), can we have that possible ?

It would be helpful if there is a way to define "Acceptance Criteria" as a separate entity.

If yes, we can get the solution of above use case as well as it would be helpful in requirement traceability to Test Cases as well from an Acceptance criteria drill down level.

Thanks,

Kanishk

[Jack Brickey]

You could certainly create a new Issuetype namedAcceptance Criteria. You need to be an admin to do this. 

project settings > issues > types > actions > edit issue types > add issuetype

is this what you are asking about?

[Bill Sheboy]

Hi @Kanishk Azad 

If you were able to do this...what would you do with the "acceptance criteria" items when the story was completed?

Issues and subtasks in Jira typically represent something that needs to be done (i.e. work).  Perhaps if your acceptance criteria were subtasks of a story, that could align with that idea of doing these subtasks to complete the story.

But if you instead want to associate them to multiple different individual issues, that would not work with subtasks.  For example story ABC-123 and bug ABC-456.  The subtasks would not be the same entity as children of different issues, a story and a bug.

If instead you create new issue types to represent Acceptance Criteria (AC), linked to other issues, how would you know when the AC are "done".  Couldn't defects be found later which you wish to associate to the AC used earlier?

Kind regards,
Bill