We have recently migrated our JIRA instance from on-premise server data centre JIRA to JIRA Cloud (for 2,000 users)
We've hit a problem with a custom field that is set to "Cascading Select Searcher"
Now that the migration has completed, in the issue layout for a project that uses this custom field, we see:
Coming Soon - "We can't show this field type in the new issue view yet, but we're working on it"
This custom field is used to assign issues in our "Portfolio-wide" views to the correct Group, then team - within our company, so it is big deal for us.
Going into the Administration for this custom field, we can still edit the options fine at both levels of the select list (parent & child)
So you can control the values in the field just fine.
What gives? Looks like this field type is planned to be supported, but given we've been using it in JIRA Classic for a couple of years now - seems odd that you can't even display the field on the issue type, now we've completed the migration.
If we *can't* use the "Cascading Select Searcher" type, what do you recommend we do to retain our data and the same functionality?
If we created 2 simple select fields & batch moved the data into them, the date updated for each issue will change, plus we lose the ability to choose the correct "Group" which then filters to the correct "Teams" within that group.
This is basic functionality for us, what do you suggest?
