-
Sub-task
-
Resolution: Fixed
-
Low
-
None
-
None
Hi everyone,
This issue has now been fixed. When an option for a cascade custom field is disabled, this will no longer appear in the list from the new issue view.
Thanks
Tha Atlassian Cloud team
Issue Summary
We have a custom cascading field called Tribe & Squad which we use heavily for our metrics reporting. There are some Squad options that we've disabled in the custom field default context and although those options are correctly disabled in the Jira Old View, however, they remain enabled in the JIRA New View.
Steps to Reproduce
- Create a cascade custom field.
- Add options in the custom field and in each option add cascade options.
- Link this custom field with a screen.
- Disable any cascade option.
- Open the issue view using the new issue view.
- Check the available cascade options in the custom field.
Expected Results
When selecting the custom field options and checking the cascade options, the cascade options that I've disabled is not appearing on the drop-down list using the new issue view.
Actual Results
When selecting the custom field options and checking the cascade options, the cascade options that I've disabled are still appearing on the drop-down list using the new issue view.
Workaround
There is no workaround.
- duplicates
-
JRACLOUD-76259 Even disabling the cascading field second option it will continue to appear in the view screen
- Closed
- is duplicated by
-
JRACLOUD-78186 Disabled cascading value is seen on issue create screen
- Closed
-
JRACLOUD-76259 Even disabling the cascading field second option it will continue to appear in the view screen
- Closed
- mentioned in
-
Page Loading...
- relates to
-
BENTO-9207 Loading...