You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm having this issue. There is another question on it but it has an accepted answer that does not solve the problem. https://community.atlassian.com/t5/Jira-Service-Management/The-mysterious-quot-Category-quot-field-at-the-issue-level/qaq-p/2088328
Problem: There is a Category field in my Issues in Business Projects but it can not be interacted with.
When creating an issue there are no options I can select. In addition any text I enter is automatically cleared when I exit the input:
In the List feature, I can sort by Category but everything is just put in one "Uncategorized" group:
In Jira settings > Issues > Custom Fields it shows the Category field but it is Locked and the "type" is Unknown. I am the highest level admin for the product and then entire Jira application and yet I can make no changes to it.
Refer to this documentation for how to add values to the Category field for your Business project.
I am facing the same issue, and it does indeed seem like a bug...
My problem is that even this solution doesn't work for me.
I can type in a category and I get the option "*Test* (New category)" to add a new category, but when I press Enter or click on the suggested new category , it doesn't save it, it just turns blank again. Anyone facing the same issue? Solutions?
After pressing Enter / clicking on the "new category" option, there is still no category added:
I suspect there has been an update to the functionality since I originally responded to this post. I don't believe that at that time the field displayed the "Add Category" option.
I see the same behavior as you now.
I recommend that you raise that issue directly with Atlassian Support.