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

What Status category would deferred, Won't Fix and Invalid issues fall in?

I am trying to add a few new statuses to JIRA for bugs raised internally, as well as for customer support issues. However, I am not sure which category to map these statuses to.

1. Deferred: We will not fix this immediately, but will consider fixing this in future

2. Won't Fix: The issue cannot be fixed

3. Invalid: This is not an issue, but was interpreted wrongly as one

As I understand, I cannot modify the existing list of status categories. Any workaround?

2 answers

1 vote
nic Community Leader Nov 09, 2017

The status categories are quite clear and there isn't really anything they don't cover. 

To do:  We have not started, and/or we are going to look at it.  This covers your "deferred" - you're going to look at it later, just not now.

In progress:  We are doing something about it

Done:  We have done it, or we are not going to do it, so we remove it from our list.  This covers your "won't fix" and "invalid" status because it means "no more attention required"

Arguably, there's a fourth category, for "held" or "deferred", but then you start getting into a mess about when you're going to pick it up again.  It's far better to use to-do or in-progress for these, because, well, you are still going to do them.

Thank you. What you have mentioned is how I have configured it at the moment. Wanted to confirm if that is the right way

nic Community Leader Nov 12, 2017

Alexey does have a good point, "one status, many resolutions" is just as good an approach as " three status".  You should have a think about whether your users need three status or three resolutions here.

"Done" as a status, with different reasons (resolutions) for the issue being done, makes sense.  The issue is ended, and the users can report of resolutions if they want to look at "why it is done".

But in many cases, you want three separate status, because it's an immediate view of why an issue won't have any more work done on it.

Which ever way you are doing it now, I would not change it, unless there's a clear reason to do it to improve your reporting!

Agreed. I am trying to figure out how to define multiple resolutions for the same status

nic Community Leader Nov 12, 2017

You can make a logical connection between them, but, off-the-shelf, Jira does not.  You can define any resolution you want for any status, because they have no direct connection.

  • A status is where the issue is in the workflow.
  • A resolution is a flag that says "issue is finished with" and (hopefully) tells the humans why it is finished.

There is no forced relationship between them in Jira (much as I would like one, it's not there.  Making it be consistent is part of the job description for a Jira admin)

Like Payal Barad likes this
0 votes


Your statuses look like resolutions. I would make them resolutions. 

You can read more about resolutions here

Thank you. I see what you are saying, and it does seem to make sense. I will give this a shot. Currently no resolutions defined

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Calling all Jira Cloud users! Give us feedback on our exploration of a new navigation.

Hi everyone! My name’s Matt and I’m a product manager at Atlassian. I work in the navigation & findability space for all our Jira Cloud products. We’ve been working on trying to improve the exp...

1,045 views 16 12
Join discussion

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