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?
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.
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!
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.
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)
Your statuses look like resolutions. I would make them resolutions.
You can read more about resolutions here
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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!
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