We have noted that Cascade Select fields are now *supported* the new "Issue View".
Previously we had instructed all our users to switch to "Classic" Issue view, in order to use a critical field, of type "Cascade Select".
As users can now use "Cascade Select" fields in issues, we have relaxed our policy and allowed users to try out the new "Issue View".
However we have found a bug.
In the context for these fields, we have *disabled* a number of values, that are no longer used. We wish to keep these *disabled* values in the context, as legacy issues contain this data, which is searchable for reporting.
However, in the "New Issue View" - the disabled values can be selected & entered into new issues.
See attached screenshots.
Context of parent list:- (see option 7, which is disabled)
See Issue Edit view, using "New" Issue view. Disabled value can be selected.
This bug is allowing bad data to come into our issues.
Please acknowledge, in the mean-time we must instruct our users to switch back to "Classic" view.
I strongly recommend posting a bug report to Atlassian via the contact form here: https://support.atlassian.com/contact/#/ as they can acknowledge a bug via that way or point you towards an existing bug reported to cast your vote.
If your old values can be mapped to new values, you could also create a JQL query that searches for issues created with old values after a certain date (by searching the create date of the issues) and then bulk editing them to the new values.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
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