Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

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

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

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.

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?

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

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