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

Bulk Change shows a duplicate "not available" option in single select fields where a value has been set

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 8.8.1
    • Bulk Operations
    • None

    Description

      Problem

      When the Bulk Change tool is used to make changes to a Select List (single choice) field where some of the issues have the value already set, a duplicate value appears in the dropdown list with the suffix "(not available)".

      Environment

      Jira 8.8.1+

      Steps to Reproduce

      1. Create a new Select List (single choice) custom field with the options A, B and C.
      2. Create a new issue and set the custom field's value to A. Note that when editing the field, the dropdown list contains only the values None, A, B, and C.
      3. Perform a search which returns only the newly created issue, e.g. "key = <issue key>".
      4. Perform a bulk change and try to set the custom field's value. Note that the dropdown list for the field in the bulk change tool contains the values None, A, B, C and A (not available):
      5. Cancel the bulk change and set the custom field's value to B.
      6. Perform the bulk change again. Note that the dropdown list for the field in the bulk change tool now contains the values None, A, B, C and B (not available):
      7. Cancel the bulk change and set the custom field's value to C.
      8. Perform the bulk change again. Note that the dropdown list for the field in the bulk change tool now contains the values None, A, B, C and C (not available):

      Expected Results

      The dropdown list for the field in the bulk change tool should be consistent with that shown while editing the field from the issue view, i.e. it should contain the values None, A, B, and C.

      Actual Results

      The dropdown list for the custom field in the bulk change tool contains the values None, A, B, C, and a duplicate of whichever value the field is currently set to with the suffix "(not available)".

      Workaround

      No workaround is currently available.

      Notes

      This issue appears to be a side effect of the fix for JRASERVER-62455: Changing a custom field configuration changes the values of custom fields when issues are edited, which was included in Jira 8.8.1 and later.

      Attachments

        1. Duplicate value A.png
          Duplicate value A.png
          30 kB
        2. Duplicate value B.png
          Duplicate value B.png
          28 kB
        3. Duplicate value C.png
          Duplicate value C.png
          27 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              8379abf86dad Marcus Fong
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Backbone Issue Sync