Has anyone, recently, migrated cascading fields to a single select field? I have seen some old posts from https://community.atlassian.com/t5/Jira-questions/Copy-Cascading-Select-value-to-Single-Select-field/qaq-p/361532 that look like it may work, but the solution didn't work as expected. I can try spending more time to fiddle with it, but I thought I would ask the question in case someone else had a similar experience.
Reason I am doing this:
Assumptions and Requirements:
- History of the cascading field isn't important
- One off mass update
- JQL support would be great, but I can pull that from the old post above if necessary
- Concat the cascading field when migrating
-- Given (cascading): L1: Applications, L2: Foo
-- Expected (single) : Applications Foo
-- Given (cascading): L1: Systems, L2: None
-- Expected (single): Systems
-- Given (cascading): Empty (i.e. field isn't filled out)
-- Expected (single): Empty (i.e. field isn't filled out. flexible on this though if it will help future people because I can bulk edit and wipe the field away)
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
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