The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Implications of changing fields to CASCADING SELECT fields
Deleted user
May 6, 2020 edited
I have 2 drop down fields currently - both are SELECT LIST (single choice) type.
I would like to request to have both the drop down fields converted to CASCADING SELECT LIST so that the list in the second depends on value in the first.
Also, I was going to change my values in both these lists involved in the Cascade.
Question is : I have over 2000 Jira Tickets for which the values as they exist currently are present. I would like to keep it that way for past tickets. If I request the above field type and data values change, will I lose all the old values that I have on these 2000 historical tickets (since those values now don't belong to the drop-downs anymore) ?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
TAGS
Community showcase
Atlassian Community Events
Copyright © 2026 Atlassian