Ho can I convert custome field type for a cascading select to a single select list?
I want to get rid of 2nd level cascading fields without creating a new single select list and retyping all 1st level options.
There's no way to do this - the data is incompatible.
You have to design a new structure that includes both top level and secondary levels (assuming you want to keep both), manually put that into a new list of options for a new field, then work out how to move the data from the old field to the new field.
You've said "ondemand" so there's no database scripting you can do (not that I would recommend that in this case, unless you've got a full test system to try it on and very good backups), and I don't think you can run Jelly to do it. You might be able to use REST to remotely perform the task, but it still may be faster to manually type it in.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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