This question is in reference to Atlassian Documentation: How do Story Points get burnt down and reflected on the Burndown Chart
We currently have a five-column Agile board:
To Do --> In Progress --> Under Review --> Awaiting Deployment --> Done
Each column represents a key step in our process - we start work (In Progress), and when we think we're done, we ask the client to review it (Under Review). Once they've accepted it, we package it up and make it ready for a weekly deployment (Awaiting Deployment). Only after it's deployed, it becomes, finally, "Done."
This leads to problems with our burndown charts and our sprints. Rather than a smooth burndown line, we only get two big cliffs during our two-week sprint, because we deploy weekly, and after deployment it becomes "Done."
What I would like to do is have story points burn down when the work goes into the "Awaiting Deployment" column, or the "Done" column (some stories are configuration and don't require deployment).
However, from what I'm seeing here, the only way that story points in JIRA are ever burned down is when stories are dragged in the right-most column. Is this really true? Is there no way, not even with a workflow post function, to burn down points when a story hits a column that isn't the farthest to the right?
There are 2 options where JIRA Software can consider a burndown (hence a change in the burndown charts).
So depending on what you need here, you can use option 1. If you really need to use option 2, there are options in the Agile board to set resolution on any column (regardless of status).
If you have the correct permission, go the "Board > Configuration > Columns >Estimation" then choose what setting do you like.
Hi Gabrielle! Thanks for the quick answer.
We're only using Story Points (we don't do time logging or estimation), so option 1 listed here won't align with the current process.
For option 2, "Closing An Issue," I've already tried using a Post function in our Workflow to set a Resolution when we transition into the "Awaiting Deployment" column. When I drag an issue into that column, I can see that a resolution is set (the Issue title gets
strikethrough and the issue's Resolution field updates), but the story points still won't burn down until the task lands in the very last column to the far-right.
Here's what the burndown chart data table looks like currently (with resolutions set on any transition into "Awaiting Deployment"):
Screen Shot 2016-07-20 at 8.56.13 AM.png
So when I drag the task into the very last column ("Done"), I get a burndown and a log in the data table as "Issue Completed." (This is expected behavior). But when I drag the task back out into the "Awaiting Deployment" column (which also sets a resolution via Workflow post function), it logs as "Issue Reopened" and the story points burn back up.
The way we'd like it to work is that the issue is still considered "Completed" regardless of whether it's in the "Awaiting Deployment" column or the "Done" column and the points burn down when the issue transitions into either column.
For reference, this is what our "Estimation" screen and "Column" screens look like on our board currently:
Screen Shot 2016-07-20 at 9.01.52 AM.pngScreen Shot 2016-07-20 at 9.02.08 AM.png
And here's a task that is in the "Awaiting Deployment" column, with a resolution set, but for which points have not yet burned down:
Screen Shot 2016-07-20 at 9.04.09 AM.png
Hi, we used a solution found in another thread.
Basically we have changed to use the remaining time estimates instead of points burn down, and we have a trigger set up to automatically set the remaining time to 0 when a ticket is moved to our "done" status (prior to the "released" one)
(Original solution link)
Not sure why Atlassian does not allow multiple statues to be reflected as a completed status for burndown/burnups. Using an empirical process, the dev team meets their definition of done and then a Product Owner accepts the work. Both of those statues should be able to be considered complete and be reflected in any burndown/burnup. Atlassian - make it so!
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 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