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

      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.

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


            we are using the Jira data centre 8.20.10  and the issue is not yet resolved, you can see the screen. It is a transition screen and I have made it mandatory with the JSU field required validator.

            SOHAIL SHAIK added a comment - we are using the Jira data centre 8.20.10  and the issue is not yet resolved, you can see the screen. It is a transition screen and I have made it mandatory with the JSU field required validator.

            ksingh4 added a comment - - edited

            Hi,
            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.

            Thanks

            ksingh4 added a comment - - edited Hi, 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. Thanks

            Tokhirjon Sirojiddinov added a comment - - edited

            What a shame for Atlassian that they cannot help people to fix this bug !!!!
            The priority - low = never?!   (hope it is not - unless you pay for it

            Tokhirjon Sirojiddinov added a comment - - edited What a shame for Atlassian that they cannot help people to fix this bug !!!! The priority - low = never?!   (hope it is not - unless you pay for it

            3 years later, and no resolution? This is preventing me from putting critical SOX compliance guardrails into our ticketing flow. Please elevate the priority of this bug ASAP.

            Scott Hartman added a comment - 3 years later, and no resolution? This is preventing me from putting critical SOX compliance guardrails into our ticketing flow. Please elevate the priority of this bug ASAP.

            Still broke over two years later. C'mon Atlassian!

            Russell Forbes added a comment - Still broke over two years later. C'mon Atlassian!

            I am looking for an update on this. This is really important for the customer. Anyone, please respond?

            Aswathy B.H added a comment - I am looking for an update on this. This is really important for the customer. Anyone, please respond?

            IBEJAOUI added a comment -

            any updates? i am looking for a solution, but it seems there is none.

            IBEJAOUI added a comment - any updates? i am looking for a solution, but it seems there is none.

            It is disappointing that a bug like this hasn't been fixed in 2 years.  Our customer's first comment looking at our form was why there is a None option when one of our fields is selected by default and to remove None.  Please look into fixing this bug.

            PJ Stevens added a comment - It is disappointing that a bug like this hasn't been fixed in 2 years.  Our customer's first comment looking at our form was why there is a None option when one of our fields is selected by default and to remove None.  Please look into fixing this bug.

            Unbelievable!  This issue was logged in 2020 and it still presents  a problem to your users! Are you planning to do anything about this at all as it takes away from the professional image  and service we want to present to our customers? 

            Sonia Forssman added a comment - Unbelievable!  This issue was logged in 2020 and it still presents  a problem to your users! Are you planning to do anything about this at all as it takes away from the professional image  and service we want to present to our customers? 

            Yeah... me too. :/

            Andre Schmidt added a comment - Yeah... me too. :/

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

                Created:
                Updated:
                Resolved: