Hey guys,
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 6.2.5.1
Thank you very much!
Regards,
Sandro
You are right, it's the right most column in a board or the status which is being associated with that column.
You could think about using an additional kanban board to monitor the states after "developement" is over...
Hey Christian,
Thanks for clarifying that :-)
It looks like we'll go with two "Scrum" boards now. We'll see how practical that'll be.
Sandro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.