I have researched and found answers, which probably relate to different versions of the software and maybe also to Agile and none agile. Thus here the clarifying question:
What is the criteria of the burndown chart for considering an issue to be done in Jira Agile? The only answer I can really relate to and verify is that all states in the right most column in a board are considered done.
What didn't seem to have an effect (at least not consistently) seems to be:
- emitting the "Issue solved" event
- setting the "Resolution = fixed" property
We have a situation, in which the end of development isn't the end of the life of the issue in our system, but what comes after it only constitutes for a fraction of the time. We'd thus like to consider an item completed earlier than the "Closed" state.
We are using JIRA 6.0.4 with Agile version 220.127.116.11
Thank you very much!
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs