-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
2
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem Definition
It is currently not possible to create a status without any Category via the JIRA UI.
Suggested Solution
It would be good to have the possibility of manually selecting the option No Category via the UI while editing or creating a Status.
Workaround
It is possible to edit the category directly in the database, using the steps below:
Take a Backup from your JIRA Database to revert back if there are any problems.- Stop JIRA.
- Run the SQL Query below in the database for modifying the category of a status to "No Category":
UPDATE issuestatus SET statuscategory = 1 WHERE pname = 'STATUS_NAME';
- Start JIRA.
- is related to
-
- Gathering Interest
[JRACLOUD-44020] As a JIRA Admin I would like to configure statuses without any category
New user of JIRA Software, I am still trying to reproduce the workflow of our current system in JIRA.
I have a problem with the fact that any new issue will be in "Open" status, thus classified in the blue "To Do" status category.
We would like to reproduce our current toolset "New" status without any status category, for example to help us triage newly created issues and get rid of spam issues, or excessive automation-created issues, or reclassify some end-user poorly created issues, BEFORE they make their way to the dev/support pipelines and pollute the boards.
JIRA Software Cloud has such a category-less status in the "Business" / "Document Approval" model :
The "Draft" status has *No status category.* This category-less status is between the "To Do" and "In Review" categorized statuses in the Doc.Approval sample (which is a bit surprising, by the way).
Issues in the sample project with the "Draft" status appear in the summary with "No category", which is just fine.
I would very much like to include category-less statuses in my "Software" workflows.
As Jira ServiceDesk is creating statuses without category itself it should become possible to do this by manual action too. Or to prevent the existence of non-category statuses
Partial workaround for JIRA Software Cloud (no access to the database) :
By creating a sample project from the "Business" / "Document Approval" template/model shown in my previous comment, I was able to use the "Draft" status in my own workflows for other projects, since the statuses are global for the instance.
This gives you a single status without a status category, that you will not edit (because the UI then requires that you choose a category).
Of course, there is some cleanup to do after that, to get rid of the sample project and its various schemes....