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

0 votes
Accepted answer

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.

https://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Field#ConfiguringaCustomField-configureConfiguringacustomfield

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,680 views 18 21
Read article

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