IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-45618

Allow no or null values in radio buttons & single select fields

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      It is currently impossible to create a yes/no field without a "None" option added if the field is not "Required"

      The problem with this approach is the field may not come into play until resolution time.

      So if I want to have a field like "Is X required?" and have a yes/no I can't do it, because:

      • Making it required means the user needs to answer that on issue creation
      • Making it optional throws in the "None" value

      This is nuts. Other fields can be null if optional, why not these?

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-45618

            Allow no or null values in radio buttons & single select fields

              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

                It is currently impossible to create a yes/no field without a "None" option added if the field is not "Required"

                The problem with this approach is the field may not come into play until resolution time.

                So if I want to have a field like "Is X required?" and have a yes/no I can't do it, because:

                • Making it required means the user needs to answer that on issue creation
                • Making it optional throws in the "None" value

                This is nuts. Other fields can be null if optional, why not these?

                        Unassigned Unassigned
                        316cf5f3c5e2 Rob Horan
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            316cf5f3c5e2 Rob Horan
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated:
                              Resolved: