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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to restrict a cascading list in a custom field

How to restrict a cascading list in a custom field in Jira Service desk 

I have a custom field Report issue and a bunch of cascading list options. 

On my customer portal i do have various customer request types 

For example I want to choose "Get IT Help " in my portal and when I click report issue i want to see all the options under the custom field

But when I choose " Open a Service Request " in my portal and I want to use the same custom field report issue and limit the visibility of the options ?

How can I achieve this ?


1 answer

Hi @Baris Sehitoglu,

Custom fields in Jira have a context. It allows you to configure different behaviours of your field depending on the project(s) or issue type(s) they appear on. It is possible to configure multiple contexts for a single custom field and that includes showing different options to your users. Take a look at Atlassian documentation to learn more about configuring context.

In the scenario you describe, it is important to note that you cannot configure different contexts based on the request type in your service desk. If you want to show different options on different requests, they have to be associated with different issue types. That may require you to redefine the mapping of your request types in the portal to different issue types.

Hope this helps! 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events