In jira release burn down report, I could not find out how added work and remaining work is being calculated.
I wanted to see the tickets as well which were added to the release.
this chart shows all issues that are in an specific release, it means that whenever an issue is placed in the release and also is estimated (time or story points), it would be shown in release burndown report.
so you can see all estimated issues (open or closed). in the report, for each sprint it shows all the remaining tasks in the beginning of the sprint (total bar) and the light green bar shows completed tasks in the sprint. also light blue bar shows the remainig tasks.
dark blue bar shows tasks that were not in the release in the beginning of the sprint but were added and estimated during that sprint.
below is a description of these parts:
also you can see here: https://confluence.atlassian.com/jirasoftwareserver0713/release-burndown-965542710.html
hope it has helped.
Thank you for the reply but unfortunately I'm not able to see the chart that you have attached.
I need some clarity on this " whenever an issue is placed in the release and also is estimated (time or story points)"
Lets take for an example below chart:
In the above chart, for sprint 2 we have 5 added story points and 79 remaining, I wanted to find out which are the tickets/issues who contribute to get that number 5 or 79.
For completed story points which is 10 for sprint 2, I can scroll down the release burn down report for that version and distinctively see the tickets which contributes to get the number 10 but for remaining and added I can not see the tickets information.
I would be really helpful, if there is a way to see the details (either in backend db or jiira app).
aha, there is no easy way to see the detail af added and remaining issues.
you can see the Added tasks by searching like this JQL:
project = X AND fixVersion = 1.3 AND fixVersion was not 1.3 BEFORE 'TIME'
*1.3 is the target version and 'TIME' is the start date of that sprint
and for remaining task:
project = X AND fixVersion = 1.3 AND fixVersion was 1.3 BEFORE 'TIME1' AND resolution was Unresolved AFTER 'TIME2'
*1.3 is the target version and 'TIME1' is the start date of that sprint and 'TIME2' is the end date of that sprint
Introduction In this article we describe the complexity of managing release cycles of complex IT solutions that comprise of a number of Apps, Service and/or Microservices. In particular, we will tou...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events