I am looking to implement the following:
1. A user will make a selection from a dropdown list (customfieldId_11111).
2. Based on the selection from the dropdown list, another field (customfieldId_22222), which is a multi-select field, will display options, which can be selected.
Why not using the cascading select custom field?
One user can set only the 1srt component, and other user may choose the 2nd component based on the previous selection.
Is there any requirement to store the values in two separate custom fields?
Ops, I didn't realized that.
You should embed a script in the multiselect description that reads the single-select value and enables/disables the corresponding options in the multiselect.
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...
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!
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