Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


I want to limit the status that's visible to the customer from the customer portal in JSM.

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. 


Status issue_JSM.png

1 answer

0 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 08, 2023 • edited

@Priyadharshani Pandiyan -

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 (

Again, Sorry.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Thanks for the update, Joseph. 

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events