Resolved items reduce issue burndown, but when Closed the issue burndown rises

When I mark an issue as RESOLVED (using either the Greenhopper task board or JIRA) then my issue burndown reduces by 1. This is what I expect.

However, when I then mark the same resolved issue as CLOSED, the issue burndown returns to original level. It is as if I have REOPENED the issue.

If I RESOLVE the issue again, the issue count goes down but again on CLOSE the count returns to original value.

My only solution is to leave all issues RESOLVED and never mark them as CLOSED.

Can anyone shed any light?

2 answers

1 vote

The count in the chart is based on the resolution field. See if the resolution is cleared when the issue is moved from "Resolved" to "Closed".

Might be in the workflow post functions or you are clearing it on screen.

Thanks for your post Jobin. I checked my issues (and just double checked now looking at the issue history) and they all have a resolution of "Fixed" or "Won't Fix". I have only 4 issues OPEN and 15 issues CLOSED.

I am wondering if there is a way of making the CLOSED Status have another meaning?

We are running our own custom workflow, but it's based on the default JIRA workflow and always prompts for a resolution on RESOLVED or CLOSED.

Any help very much appreciated.

The burn down relies on the CATEGORY of a status.

Each status belongs to one of three categories: New, In Progress or Complete. 

Note that these category are visualised by the colour of the status text (Blue, Yellow, Green respectively) 

I imagine your Closed status is put in category New or In Progress instead of Complete. (check if the closed status appears in blue or yellow on your JIRA issues)

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Sarah Schuster
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

13,256 views 15 14
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you