We want to improve our reporting in Jira Agile. Our situation is as follows:
Right now the burndown occurs after we do a release (after we verify our items are workin on the live site we move to "Done"). This means that as it stands now we see no burndown until release day which makes our reporting totally useless instead of being transparent.
1.) How can i configure the boards to burndown once an issue is moved to "development complete" instead of needing to wait until release day?
2.) I ideally want to do this in the agile board so its all in one place. Is there a way to do this? If there is not a way to do this what is the next best solution?
As an additional note this would be a non-issue if we were in continuous integration but we are not there yet, so this is why I need this exception.
Based on this issue (https://jira.atlassian.com/browse/GHS-5522), I don't think your request will be fulfilled.
Is there a way to do this? If there is not a way to do this what is the next best solution?
Have a second Kanban board that starts at the end of the development process. You can then use the Kanban reports to track the release (https://confluence.atlassian.com/display/AGILE/Tutorial+-+Tracking+a+Kanban+Team)?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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