Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-37309

A Multiple CustomField Type should not enforce entering Options

XMLWordPrintable

      As of JIRA 6.2, it is now mandatory to enter at least one Option when creating a customfield that implements options. It is a wrong assumption that a user is required to enter options in a customfield. Any customfield that derives from AbstractMultiCFType and that implements options does not necessarily have to have options. It is the case of the Checklist add-on on the marketplace. By being mandatory, a user of Checklist that only needs to enter value at the issue level has to enter a dummy option and remove it later. This is not very user friendly.

            [JRASERVER-37309] A Multiple CustomField Type should not enforce entering Options

            Mariano added a comment -

            This was reported over half a decade ago. Still not love from Atlassian team? :super sad emoji:

            Mariano added a comment - This was reported over half a decade ago. Still not love from Atlassian team? :super sad emoji:

            Ivan Prikhodko added a comment -

            +1 it's really annoying, I hope a fix is coming soon

            Ivan Prikhodko added a comment - +1 it's really annoying, I hope a fix is coming soon

            Maxime Lefebvre _Okapya_ added a comment -

            We found out that the options are required at creation when the option configuration item is present in the custom field configuration screen (in `getConfigurationItemTypes`).

            A workaround would be to replace the `SettableOptionsConfigItem` from your config items to something else.

            Maxime Lefebvre _Okapya_ added a comment - We found out that the options are required at creation when the option configuration item is present in the custom field configuration screen (in `getConfigurationItemTypes`). A workaround would be to replace the `SettableOptionsConfigItem` from your config items to something else.

            Harry-Matteo Franke added a comment -

            +1

             

            Harry-Matteo Franke added a comment - +1  

            Pascal Perreault [Okapya] added a comment -

            +100. I think 6 years is enough impact gathering you can do it now.

            Pascal Perreault [Okapya] added a comment - +100. I think 6 years is enough impact gathering you can do it now.

            Ricky Lin added a comment -

            A top 10 most voted unresolved Bug reported from over 6 years ago not getting any love from Atlassian?  You bet that sounds like it.

            This behavior not only impacts native Jira Custom Fields, as well as paid plug ins where the vendors cannot do much about.  Please bump it up on your priority map and fix it already.

            Ricky Lin added a comment - A top 10 most voted unresolved Bug reported from over 6 years ago not getting any love from Atlassian?  You bet that sounds like it. This behavior not only impacts native Jira Custom Fields, as well as paid plug ins where the vendors cannot do much about.  Please bump it up on your priority map and fix it already.

            John Jessup added a comment -

            +1 to fix

            John Jessup added a comment - +1 to fix

            Fozi added a comment -

            +1

            Fozi added a comment - +1

            jlaturnu added a comment -

            +1

            jlaturnu added a comment - +1

            Deleted Account (Inactive) added a comment -

            +1 for fix, hopefully without delegating to a paid plugin.

            Deleted Account (Inactive) added a comment - +1 for fix, hopefully without delegating to a paid plugin.

              Unassigned Unassigned
              e0615f94a661 Yves Riel [Okapya]
              Affected customers:
              142 This affects my team
              Watchers:
              41 Start watching this issue

                Created:
                Updated: