Issue Statuses with (No Category) are auto-generated by Jira Service Management
Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
There are some issue statuses: (Waiting for support) & (Waiting for customer) that auto-generated by Jira Service Management are categorized with a "No Category". The "No Category" is not allowed in normal Jira usage where all statues are required to be categorized into:
- To Do
- In Progress
- Done
If the statues is changed to either three of the categories above, the category will not be able to change back to "No Category".
Details
This is just the Jira Service Management created the statuses without the requirement, it will not cause any further issues other than changing the color of some status lozenges.
Workaround
If you wanted to change it back to "No Category", you may do so by modifying the database directly as suggested in JRASERVER-44020 - Getting issue details... STATUS
Always back up your data before performing any modifications to the database. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.
- Backup your Jira database so that you can rollback if you encountered any problems.
- Stop Jira.
Run the SQL query below in your database to modify the intended status category to "No Category":
UPDATE issuestatus SET statuscategory = 1 WHERE pname = 'STATUS_NAME';
Just change the STATUS_NAME to the status name that you wanted to change.- Start Jira.