The Sprint Burn Down Gadget used in Dashboard does not seem to work reliably. Do you know if there requirements or restrictions that apply to that gadget? We are completing several sprints and the gadget no longer works.
Background info: iVinciHealth cloud JIRA account, VPNG Board/Project. There are 3-5 active sprints in that board at any given time. We do modify the content of the sprints as time goes on. We use a scrum template I believe. The gadget seems to operate correctly for other sprints and other boards.
We have customized the workflow. Both parents and children issues use the same workflow to simplify the kanban board display in the dashboards.
Any input on what affects the behavior of that gadget would be much appreciated.
It shows nothing, except the black line going from top left corner down to right bottom corner. No burn up or burn down information shown at all.
We have conjectured that changing the content of the sprint seems to have an impact, but we can pinpoint exactly as to the root cause.
It is hard to tell. The chart started to show burn down data again starting April 1, but not sure why when the day before it showed nothing. We use tempo to track time, and the tempo team crosses several concurrent active sprints. The chart still shows no data prior to April 1 even though the sprint started in March and will end shortly.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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