Populate JIRA dropdown based upon selected value in another dropdown

Is it possible to populate a dropdown box based upon the selected value in another dropdown?

For example, we have multiple software projects and each has its own distinct attributes like build versions and subcomponents.

Right now we use separate projects for each software system and it is a bit of a management nightmare since users enter their issue in a public "master" project and our support department then moves those into the appropriate software system-specific project where they are worked on and managed.

We would like to use a single JIRA project for all of our software projects but each system has different build numbers, different subcomponents, etc.

Thus, if software system A is selected which has build numbers 1.1, 1.2 and 1.3, we would like the build dropdown to be populated with those build numbers and not with any other system's build numbers. Likewise, the subsystems/components dropdown should be populated with the components of that software system.

Can we do this? How?


2 answers

I guess this is not completely achievable in the way you want. A close solution will be a "Cascading Select" custom field, even though this still needs you to manage the sync between the project versions and the values inside this cascading select.


Another option is to use the Behaviours Plugin and allow the user to use free text fields for entering the Component and Version and add a server side validation to check whether these values are actually okay or not.

Thanks Renjith. I saw the Behaviors Plugin which might have some uses for us but we need the dropdown capability to eliminate guesswork. I'll take a closer look at the Cascading Select to see if that might work for us.

Steve -

We have a similar requirement and I appreciate if you can share the implementation. 

Thanks ! 


 we have the same requirement also. I really appreciate if you can share how you did it



It would require manually keeping track of your build numbers and project ID, but you can acheive this using JavaScript in JIRA;


This might be a lighter-weight solution than a plugin.


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,712 views 17 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