Besides adding a status, what's the best field to assign "not doing" to an issue

annette mattox November 16, 2020

I want to filter certain issues out of a project data set because we are not going to do them and we want to close out the project (burn down).  We do not want to create a status for them.  We identify the project with a value in the component field.  What field should I use to assign the value "not doing".  

1 answer

2 votes
Kat Warner
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
November 16, 2020

We use the "resolution" field for this. We have "Won't do" alongside 'Resolved' and a few others so we have the ability to report on why issues are closed.

annette mattox November 16, 2020

Thank you!

Does an issue have to be in "done" status before you can assign a resolution value?  If so, how do you keep those "not doing" issues out of your burndown metrics?

Kat Warner
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
November 16, 2020

You will need to update the estimation statistic on any "not doing" ticket to zero so they do not affect the burn down calculations.

Suggest an answer

Log in or Sign up to answer