Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-31129

Better handling of "none" option in custom field drop-downs during issue update.

    XMLWordPrintable

Details

    • Bug
    • Status: Gathering Impact (View Workflow)
    • Low
    • Resolution: Unresolved
    • None
    • None
    • Issue - Fields
    • None

    Description

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

      • Create a drop-down custom-field with options A, B, and C.
      • Create an issue and leave the value for the field as None.
      • Edit the settings of the custom field and set default value to C.
      • Edit the field config and set the field as required.
      • View the issue you previously created - note that the field still has no value.
      • Edit this field.

      Actual: The drop-down is now set to A.

      Expected: The drop-down should include the "none" value and have this set as its value. (it should fail on validation if the user does not set a value)
      (This would be consistent with what happens on Create Issue when a CF is mandatory but has no default.)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mlassau Mark Lassau (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: