Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-70555 New Issue View in Jira Cloud
  3. JRACLOUD-74233

Disabling the cascade options in the custom field doesn't get any effect in new issue view

    XMLWordPrintable

Details

    Description

      Atlassian Update - 17 June 2021

      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

      1. Create a cascade custom field.
      2. Add options in the custom field and in each option add cascade options.
      3. Link this custom field with a screen.
      4. Disable any cascade option.
      5. Open the issue view using the new issue view.
      6. 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.

      Attachments

        Issue Links

          Activity

            People

              vvasudevan@atlassian.com Venkatesh Vasudevan
              a4d87f7c6c2a Guilherme A
              Votes:
              42 Vote for this issue
              Watchers:
              40 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: