-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how your teams work and what you're hoping to accomplish with JIRA.
We have decided to close this specific request for additional status categories as Won't Fix. The finite set of status categories allows us to build useful features on top of them, like completion progress indicators for Epics and Versions.
We recognize that for many teams, most of the steps in a workflow are "In Progress" and that it can be difficult to distinguish them. Here are some strategies:
- Add additional columns to your board for different workflow states. You can have several "In Progress" columns to represent concepts like "In Development" or "Under Review".
- Use the card colors based on JQL queries feature (documentation) to define your own colors for workflow states. I've created this suggestion in the JIRA Agile project to improve this in the future: GHS-11666
- Use JIRA Agile card layouts (new in JIRA Agile 6.6) to show the workflow state on the card (documentation)
- To customize the display of issues within the JIRA issue navigator, consider the free third-party icnavigator add-on from Interconcept GmbH.
We do not plan to support arbitrary colors for status categories. The mapping of blue, yellow, and green to "To Do", "In Progress", and "Done" is part of Atlassian's overall visual system. Our intent is to improve how we use this pattern to communicate information in JIRA; however, we use the combination of colors and lozenges to represent concepts not only in JIRA, but across Atlassian's product suite.
Finally, there were specific requests for a "Red" status color. The main use case here was situations where an issue had progressed to the end of a workflow, but the resolution was negative (e.g. "Failed" instead of "Done"). In JIRA's structure, this connects the final workflow state (i.e. "Resolved") with the type of resolution. While there's certainly merit in this request, it has the potential to significantly increase JIRA's complexity.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
JIRA Product Manager
The new status colors in JIRA provides initial set of pre-defined statues. It would also be beneficial to add the ability for users to add more categories to it
- is duplicated by
-
- Closed
- relates to
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- was cloned as
-
- Gathering Interest
-
- Gathering Interest
[JRASERVER-36241] Ability to add more categories to statuses
Dave, this should be reconsidered. We have many tickets that are 'invalid,' and right now they are being tagged as 'done', which is extremely counterproductive. We should at least be able to add one custom category.
It could be very useful to have another workflow category for status In test/In Review so we can see in recap progress bar of release page 4 colors:
Grey as to do
Blu as in progress
"new color" as in test/review
maintaining a standard approach of Atlassian
Adding more custom status categories may not be a good fix as it might affect the internal implementation of Jira features. But can we have custom groups or any other way to categorize the statuses? Since we have the option to build our own workflows with the custom status we can not put all these statuses into these 3 categories. When we make filters, status categories are becoming useless and it is very difficult to manage all the filters by adding or excluding individual statuses.
Totally agree with David.
Dave you should consider it again - adding it helps build more effective JQLs using StatusCategory instead of Statues which helps build multi-project boards and dashboards. If needed, happy to provide you with detailed cases.
In our organization we have 5 different categories of tickets and it would be nice if we could have JIRA recognize that.
Planning/Analysis -> To Do (Backlog) -> In Progress -> In Review -> Done
Within those categories we have the following statuses:
Planning/Analysis
(New Idea -> Requirements Analysis -> Stakeholder Review -> Scheduled)
To Do (Backlog)
In Progress
In Review
(QA Review -> Code Complete -> Code Review -> Testing)
Done
(Ready For Release -> Released)
We currently make it work by utilizing multiple boards and manual labor to convert issue types etc... Other larger organization I am sure have other quality assurance processes that require more customization in this area.
Example of where it would be helpful. We use an addon BigGantt to help with the planning of tickets. BigGantt has two task colouring options, Status Category and Manual. I would like to have more that 3 colours, but the colour is assigned to the category and there are only three options. If I could add another category type I would be able to organize my work better.
So big up vote from me to have this configurability.
You could all save yourself some time if you realized that Atlassian knows what is best for you. Quit trying to make your own workflow to support your business and only do it the way they say it should be done. That is why we pay them higher licensing fees each year for less and less features out of the box.
This should definitely not be "Closed" and ignored. It really limits the usefulness of Jira and it's not something we as administrators can easily edit, because believe me, we would take it into our own hands.
@DaveMeyer
This would be a very useful feature. Especially thinking about "Failed" / "Rejected" / "On Hold" etc. which is none of the predefined status categories. It's not open anymore, nothing in progress and definitely not done!
So why Atlassian is so balky about this issue? I really do not understand because it would bring so much benefit to so many users. 
So here it is 10 years later and Atlassian still won't reconsider. Atlassian has a long history of smugly substituting process for knowledge.