Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Why doesn't multi-project sprint doesn't burn down story points in multi-project board

Hi guys,

 

I have a problem, which's been haunting me for weeks now.

 

I have 5 projects in Jira. I created a filter, which displays all issues in all those 5 projects. In every of those projects I created an "All issues" board with the filter mentioned before. I also created "All issues in this project" in every project.

 

On top of all that I have a custom workflow (Open > In Progress > QA > Under Review > Closed), where Open status and Closed status are the ones from the original Jira workflow.

 

Now, when I start a sprint with issues from each of the 5 projects. The tasks that are closed don't get burned down properly on the burndown chart for any of the "All issues" boards. I can only see them burn down if I switch to the "All issues in this project" board.

Does anyone have an idea how to I fix the burndown chart for multiple projects?

Best,
Lukasz

1 comment

Are the issues in the last column of your "all issues" board?

I got it sorted out. See the order of columns is what I've been looking at all this time. That is naturally important, your final state has to be in the rightmost column in your board.
The culprit was the resolution field.

As it turns out, my workflow didn't set any resolution and in effect the tasks didn't get burned down properly in a multi-project view. They did however update in the single project view, because of the column alignment mentioned in the previous paragraph.

Updating the resolution field to "Done" did the trick for the current sprint. The previous sprints are almost good, the only but is, the issues that got closed in previous sprints are treated as removed from the sprint and their statuses are set to "In Progress", even though they are "Closed" (to verify just click at any of them).

Now there's a little caveat here. You can't directly change the value of the resolution field

Solution

1. Set resolution field in all "Closed" tasks to "Done".

1.1. To do that I added a transition from the "Closed" state to back to itself and I added a POST function, which changes the resolution field to "Done".

1.2. After that I went to "Issues and Filters", used JQL to look up all the issues which are "Closed" but have no resolution set. And then made a bulk status transition from "Closed" to itself, using the newly defined transition which triggers the POST function I added.

1.3. I deleted the "Closed" > "Closed" transition

2. Made all the future transitions "Under Review" > "Closed" set resolution to "Done"

2.1. I added a POST function to the "Under Review" > "Closed" transition and published the workflow

Note

I skipped over some steps like creating a draft of a current workflow and publishing it etc.

Corollary

To add another final status that finishes the lifetime of a ticket in a different way than "Closed", say "Rejected". Just remember to add resolution to e.g "Won't fix" or so

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira

Do you use Jira Cloud with Microsoft Teams?

Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...

377 views 1 6
Read article

Community Events

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

Events near you