I have been using behaviours to emulate a 3-way cascaded selection:
Product --> Environment --> Customers
by conditionally showing/hiding different fields - The 2nd level fields (env-A, env-B, etc.) are shown based on 1st level (prod-A, prod-B, etc.), 3rd level is based on the values of the 1st + 2nd level fields.
Sadly, on cloud, behaviours are not available, at least not in the near future (as per ScriptRunner vendor).
My plan is to use different issue types to replace the first level (e.g. 'Product Name') and then in each type I will have a cascaded select field for the 2nd/3rd levels.
All issue types will share the same workflow, and for the cascaded select field I will use different field configuration contexts (keyed on the issue type), so the screens will use the same fields.
I have not yet tested this option (contexts) on the cloud. Will report here if I encounter problems.
TL;DR: Good Riddance!
I have not done that via REST API, but here's the documentation:
The 1st type is 'cascadingselect', which is what you need.
And of course, in the UI, go to your CF link:
click on 'Create custom field', choose 'Select list (cascading)'.
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events