Issue Types drive Cascading list values in the same project

I am trying to have specific issue types of a single project drive the first value of cascading list field. When configuring a new context for a cascading list and I've noticed you can only create one scheme per project. If you select a issue type you are forced to select a project. Is there a way around this or a better alternative?

1 answer

1 accepted

You'll not be able to acheive this with contexts. As the documentation states -

A custom field can only have one context per JIRA project. So you cannot have multiple contexts for different issue types in the same project.

I'm not sure for specific solution, but you can try figuring out something with script runner

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,139 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot