Right now there are only 3 status categories - 'To Do', 'In Progress' and 'Done'. I want to create another category and associate it with my own statuses. For example, I don't want the status 'Failed' to be in category 'Done', because that changes the background of the status to green, and is like the request failed as intended. In my case request should be worked on till the status goes to 'Done', but there should be intermediate status failed with the color red.
according to https://jira.atlassian.com/browse/JRASERVER-36241 Atlassian won't enable new status category colors.
You could try an add-on (e.g. https://marketplace.atlassian.com/plugins/com.almworks.jira.colors.colors-plugin/server/overview) to improve colors of your issues based on status.
Hope that helps.
I fail to see how this answers the OP question.
"I want to create another category and associate it with my own statuses."
I don't see this issued addressed at all.
Could you confirm whether it is possible at all or not with JIRA cloud? Could it be added by installing a plugin?
As much as we hate it, the answer to, "How can I create a status category?" is "you can't." However the link provides suggestions on how to simulate custom status categories.
From the link:
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.
Won't Fix is the Resolution and not the status which probably has been "Rejected"
@Integration Team ... mm this seems a really useful feature especially for user like corporates where you have lot of projects and want to create some view / filter to highlight some important "Phases" in the company lifecycle ... which can have Different Statuses in different projects
Why is Google saying this issue is solved? I was so excited when I saw this, but then the accepted answer is that it IS NOT solved.
Every resource, attribute, and property is customizable in Jira, what is the thinking behind not making status categories so?
There are so many more status categories that are so so basic... How about "Blocked" for instance which may have several statuses associated with it? And you need a category to differentiate when a task has not been started (todo) and when it is not able to move forward (blocked)?
Please add this basic feature
Well that's misleading, inefficient, and inconsistent with the plethora of "done" statuses I get out of the box with Jira even.
This is a question (check the breadcrumbs / url), questions have answers... You don't solve a question, you solve a problem. And this is a question concerning a problem that is anything but solved.
I could see an accurate status for the problem itself being Unsolved, Never to be solved, Decided to never implement. Or maybe change the status of this to at least Answered so it makes sense. Any of which would then have a status category of Done
In a perfect world someone would figure out how to get Google to simply show the text You can't, ever on the search results page and save everyone the time and hassle.
Anyway just my two cents, cheers
That is not correct. There is a status category "To Do". We already have custom status "New". This question is about custom categories. There is no category that fits with our "New" status. The first option is "To Do" (again this is a category, not a status. each status is assigned a category in Jira). We do not want it to be "To Do" because we do not want anyone working on "New" tickets until they are moved to the "To Do" status (which is also in the "To Do" category). We also want to be able to create an "Active Issues" filter that does not include issues with the "New" status. If we add the "New" status to the "To Do" category then it will show up in the "Active Issues" filter. I hope that clarifies things. There is no category that fits our "New" issue status.
Has there been any update on this bit of functionality? I can't seem to find any way to create your own custom Categories within a Status. The ability to create custom categories and use them as the default categories are used seems like something that definitely should be supported.
Recommend revisiting the link provided in the 2018 comment above. https://jira.atlassian.com/browse/JRASERVER-36241
It appears that Jira Status "Categories" is not suited for your expectations or usage.
Recommend creative use of workflows and statuses in conjunction with unique resolutions.
Another option is to create a custom field and script your own "Category" to display expected results.
Other options discussed in the link above may also achieve the results you are looking for.
Either case, it appears that Atlassian made their decision and are not adding additional status categories at this time.
At first it was frustrating but thinking about it and the ripple effects to Releases and out of the box Reporting for example it's understandable that Atlassian have made the decision. If you think about it any work item (in or out of work) is either 'To Do', 'In Progress' or 'Done'. If you want to sub-categorise where something is within those statuses it's entirely possible in JIRA as it is in life.
Build your board(s) based on a filter that doesn't include 'new' as the 'working board', create a board with only the 'New' issues as the prioritisation board to determine what should go into 'To Do'.
Create a Kanban board and using a backlog so that the 'New' issues that aren't selected/prioritised to a 'To Do' status don't show on the (To Do, In Progress, Done) board.
How to do that you ask?
It's possible to create new issue statuses in the workflow section, then when constructing your board you choose whether to assign or not assign those statuses to show up on the board under the 'To do', 'In Progress' or 'Done' columns.
For example you can choose NOT to display 'New' issues on the board, only those that have been transitioned to the 'To Do' status.
Also boards do allow you to create multiple columns to support the desire to break 'To Do' into smaller portions of 'To Do', for example 'In development', 'In code review', 'Ready for Test', 'Ready for Release' can all be a 'To Do' status if you create them as a workflow status, you can then create columns in a board using those statuses, they are all 'In Progress' type statuses.
Yes there are workarounds. We already recognise this. Doesn't it seem odd to you however, that the To-Do status doesn't belong to the To-Do category in the scheme proposed. I'd call that a smell.
As a side note, the fact that people are searching for how to achieve this objective at all, rather than why it is missing is yet another indication of the incredibly poor UI affordability of recent versions of Jira. I've been a Jira user since the first release in 2002 and I still waste time trying to figure out how to accomplish what should be simple configuration tasks. It sure makes it hard to sell this tool as a contractor to a new management team every few months.
I am with you that Jira leaves many things to be desired, however I find this set of status categories pretty comprehensive: Each item in any workflow I can imagine is either waiting to be processed (To-Do), being worked on, or finished. I really can't imagine a fourth status category. Atlassian may be doing a poor job explaining this, but the concept is sound.
It's actually quite simple:
Bringin all this together: When you have a new item, the work required to move it to the next stage might be to categorize, prioritize or describe the item in more detail. In such a workflow a new item is waiting to be categorized, prioritized or described, it other words, new items are of the category To-do.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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