Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-75541

Radio buttons custom field set as required and with a default value still shows "None" as an option

XMLWordPrintable

      Issue Summary

      Radio buttons custom field set as required and with a default value still shows "None" as an option.

      Steps to Reproduce

      1. Create a radio button custom field and add some options.
      2. Select one of the options as the default one.
      3. On a classic project, set this field as required.

      Expected Results

      On the edit issue screen, it only shows the options that admins added on the field.

      Actual Results

      It still shows "None" as an option and if the user selects "None" it shows an error.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available.

      Update: the “None” option only appears if you set a transition screen, because those screens use the old issue view.

      **

      Update

      We have triaged this bug and found out the issue is no longer replicable to customer instances.
      We can confirm the expected behaviour as follow.

      1. When we have a custom radio select field marked as not required it displays  `none` option in issue view/edit and issue transition screens but will not in issue create screen.
      2. When we mark a custom radio select field as required it will not display `none` option in all issue view/edit, transition screen and issue create screen.

      As above mentioned behaviour description invalidates the bug. So we can mark it as closed/fixed now.

        1. Screen Shot 2020-11-11 at 18.11.20.png
          Screen Shot 2020-11-11 at 18.11.20.png
          20 kB
        2. Screen Shot 2020-11-11 at 18.11.39.png
          Screen Shot 2020-11-11 at 18.11.39.png
          14 kB
        3. Screen Shot 2020-11-11 at 18.16.16.png
          Screen Shot 2020-11-11 at 18.16.16.png
          16 kB

            [JRACLOUD-75541] Radio buttons custom field set as required and with a default value still shows "None" as an option

            Andrey Lazarev made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 911724 ]
            M.Shimizu made changes -
            Link New: This issue relates to JRACLOUD-83746 [ JRACLOUD-83746 ]
            Arbaaz Gowher (Inactive) made changes -
            Assignee New: ksingh4 [ 6196750b3f44 ]
            Arbaaz Gowher (Inactive) made changes -
            Link Original: This issue is blocked by JRACLOUD-78919 [ JRACLOUD-78919 ]
            ksingh4 made changes -
            Description Original: h3. Issue Summary

            Radio buttons custom field set as required and with a default value still shows "None" as an option.
            h3. Steps to Reproduce
             # Create a radio button custom field and add some options.
             # Select one of the options as the default one.
             # On a classic project, set this field as required.

            h3. Expected Results

            On the edit issue screen, it only shows the options that admins added on the field.

            !Screen Shot 2020-11-11 at 18.16.16.png|width=338,height=122!
            h3. Actual Results

            It still shows "None" as an option and if the user selects "None" it shows an error.

            !Screen Shot 2020-11-11 at 18.11.20.png|width=268,height=127!

            !Screen Shot 2020-11-11 at 18.11.39.png|width=278,height=72!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available.

            Update: the “None” option only appears if you set a {*}transition screen{*}, because those screens use *the old issue view.*

            **
            h3. Update



                          		New: h3. Issue Summary

            Radio buttons custom field set as required and with a default value still shows "None" as an option.
            h3. Steps to Reproduce
             # Create a radio button custom field and add some options.
             # Select one of the options as the default one.
             # On a classic project, set this field as required.

            h3. Expected Results

            On the edit issue screen, it only shows the options that admins added on the field.

            !Screen Shot 2020-11-11 at 18.16.16.png|width=338,height=122!
            h3. Actual Results

            It still shows "None" as an option and if the user selects "None" it shows an error.

            !Screen Shot 2020-11-11 at 18.11.20.png|width=268,height=127!

            !Screen Shot 2020-11-11 at 18.11.39.png|width=278,height=72!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available.

            Update: the “None” option only appears if you set a {*}transition screen{*}, because those screens use *the old issue view.*

            **
            h3. Update

            We have triaged this bug and found out the issue is no longer replicable to customer instances.
            We can confirm the expected behaviour as follow.
             # When we have a custom radio select field marked as not required it displays  {*}`{*}none{*}`{*} option in issue view/edit and issue transition screens but will not in issue create screen.
             # When we mark a custom radio select field as required it will not display `none` option in all issue view/edit, transition screen and issue create screen.

            As above mentioned behaviour description invalidates the bug. So we can mark it as closed/fixed now.
            ksingh4 made changes -
            Description Original: h3. Issue Summary

            Radio buttons custom field set as required and with a default value still shows "None" as an option.
            h3. Steps to Reproduce
             # Create a radio button custom field and add some options.
             # Select one of the options as the default one.
             # On a classic project, set this field as required.

            h3. Expected Results

            On the edit issue screen, it only shows the options that admins added on the field.

            !Screen Shot 2020-11-11 at 18.16.16.png|width=338,height=122!
            h3. Actual Results

            It still shows "None" as an option and if the user selects "None" it shows an error.

            !Screen Shot 2020-11-11 at 18.11.20.png|width=268,height=127!

            !Screen Shot 2020-11-11 at 18.11.39.png|width=278,height=72!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available.

            Update: the “None” option only appears if you set a {*}transition screen{*}, because those screens use *the old issue view.*             		New: h3. Issue Summary

            Radio buttons custom field set as required and with a default value still shows "None" as an option.
            h3. Steps to Reproduce
             # Create a radio button custom field and add some options.
             # Select one of the options as the default one.
             # On a classic project, set this field as required.

            h3. Expected Results

            On the edit issue screen, it only shows the options that admins added on the field.

            !Screen Shot 2020-11-11 at 18.16.16.png|width=338,height=122!
            h3. Actual Results

            It still shows "None" as an option and if the user selects "None" it shows an error.

            !Screen Shot 2020-11-11 at 18.11.20.png|width=268,height=127!

            !Screen Shot 2020-11-11 at 18.11.39.png|width=278,height=72!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available.

            Update: the “None” option only appears if you set a {*}transition screen{*}, because those screens use *the old issue view.*

            **
            h3. Update



             
            Andrey Lazarev made changes -
            Labels Original: seems_good New: dospairing seems_good
            ksingh4 made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            UIS Original: 96 New: 97
            SET Analytics Bot made changes -
            UIS Original: 101 New: 96

              6196750b3f44 ksingh4
              adaluz Angélica Luz
              Affected customers:
              215 This affects my team
              Watchers:
              93 Start watching this issue

                Created:
                Updated:
                Resolved: