I have viewed and broken down /rest/greenhopper/1.0/rapid/charts/scopechangeburndownchart to better understand the data needed for the sprint burndown chart. This has been a nightmare! It seems that there is some creative code needed to take this info and actually recreate the sprint burndown because some of the information provided goes back into the sprint issues' history from creation all the way up to that sprint's life. For example, the sum of the remaining estimate of all issues is not clear.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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