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 configuring JSM as the ticketing tool for my organization and I would like to limit the status that's enlisted in the drop down. This drop down consists of status that has been created across all the projects in both Jira Service Management and Jira Software.
Is there a way to limit this status to just 4 or 5 in total. I have 222 statuses of which many are not being used or duplicate based on the Project Lead who created this status for their project board.
Based on my experiences/knowledges that unfortunately you cannot limit the statuses visibility from the Request portal UI dropdown list out of the box. The key thing is that the statuses are alway grouped by project. Example - You can see all the statuses associated with my project named GIAPPS JSM
The only possible workaround is to restrict customers access to project(s) that he/she is not associated. Thus, he/she will not even discovered/access those projects. In the end, the Status dropdown list will display the statuses from project(s) that they are allowed to access/submit issues again only.
This is why there should be some type of control on WF status creation implemented at your env. A lots of time, if it is not controlled or project leads are trained, there can be too many custom statuses generated for your env.
You may want to research if there are any third party add-ons which can provide you with what you are asking for via Atlassian Marketplace (https://marketplace.atlassian.com/).
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team