Not sure how easy this is to explain: for a number of teams within my company, the definition of "done" is that the initial work (changeset) is "peer reviewed" (which comes after coding) but not functionally tested. All the statuses are correctly placed in the right columns and it works as expected for the most part. I understand that this is not what Scrum and Agile preach, we're basically saying that functional testing is not sprintable; we're working on making that a possibility but it is our current reality that will not change for the immediate future.
The problem: if a ticket passes peer review and thus is "done" within the Sprint but then fails in testing also within the Sprint and the developer starts working on the fix (which changes the status to something that doesn't count as "done") and doesn't finish before the end of the Sprint, at the end of the Sprint the ticket will not count as "done" although it meets our definition.
The question: is there any way to make this sticky as in once a ticket reaches a status that is mapped to the "done" column, if that status should change to something that maps to "In progress" the ticket is still considered "done" from a Sprint retrospective purpose? I understand that it would not move into the next Sprint, we have ways to keep track of our rework within our 2 Sprint release cycles.
Any help would be tremendously appreciated. Again, I understand that it's not ideal so please don't tell me to complete testing and rework within each Sprint, we'll get there, just not tomorrow. I just want to know if there's any way to use existing JIRA functionality to accomplish this. Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.