Can a different column other than the right-most column trigger a burndown?

[Robert Bono]

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? 

[Asael Sepúlveda]

You have to create filters for each one:

 How many Issues are currently assigned to a user: Create a filter that shows every issue and use it on a pie chart gadget grouped by assignee. You can also just query for assignee = <User> to see the results size

 how many have they completed in a given period: 

1. resolutiondate < now()
2. resolutiondate < "2014/11/01" and resolutiondate > "2014/10/01"

how many estimated hours of work is assigned to them for a given period: you can use the workload gadget

[Asael Sepúlveda]

Hey Tiash,

 As for saving the reports, you can save them as filters and from there you and your users can subscribe to them in order to receive them periodically: 

https://confluence.atlassian.com/display/JIRA/Receiving+Search+Results+via+Email

 As for the workload pie chart, you do need the JIRA charting plugin and also have time tracking enabled:

https://confluence.atlassian.com/display/JIRA/Workload+Pie+Chart+Report

[Midori]

You can create this report and any custom multi-dimensional report like this:

1. Create a JQL filter that returns the issues (from all the projects) that you want to include in the report. At this point you probably want to filter these to the "given period" you mentioned.
2. With the Better Excel Plugin, create a template which exports the following raw data for each issue:

Column "A": issue key
Column "B": assignee user name (or display name)
Column "C": resolution date (if resolved) or leave it blank
Column "D": estimated hours

1.  Finally create the following Excel pivot tables:

Between column "A" and "B": how many Issues are currently assigned to a user

Between column "B" and "C": how many have they completed in a given period,

Between column "B" and "D": how many estimated hours of work is assigned to them for a given period

This should be fairly straightforward if you follow this Excel pivot table tutorial.

[Tiash Zaman]

Thanks Asael for your response. 

For the Workload Gadget – I used the  Report: Workload Pie Chart Report and got this 500 error: java.lang.NoSuchMethodError. Do I need to download and install the JIRA Charting Plugin?

Also, how can I save the reports in JIRA?