Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-12833

Asset filter attributes order is now alphabatized

XMLWordPrintable

      Issue Summary

      After updating to a release later than JSM 5.6+ DC attributes columns added to asset customfields are alphabatized. Where previously they would honor the oder the users configured them in.

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Run latest JSM DC (5.8 at writing)
      2. Create Project -> Create sample data
      3. Goto custom fields
      4. Configure "Affected Servers"
      5. Click "Edit Assets Configuration"
      6. Amend "Object attributes on Issue view"
      7. Set elements in any oder, example "Status|Server Owner|Environment"
      8. Click "Return to Jira Custom Field"
      9. Click "Edit Assets Configuration"

      Expected Results

      The array in Object attributes on Issue view should retain the order set.

      Actual Results

      The array in Object attributes on Issue view re-arranged alphabetically

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

          Form Name

            [JSDSERVER-12833] Asset filter attributes order is now alphabatized

            Brüse, Bernhard added a comment -

            We are currently evaluating JSW 9.16.0 and JSM 5.16.0 on a testing system. We can't confirm that the bug has been fixed!

            Brüse, Bernhard added a comment - We are currently evaluating JSW 9.16.0 and JSM 5.16.0 on a testing system. We can't confirm that the bug has been fixed!

            David added a comment -

            Will this be back ported to the LTS 5.12.x?

            David added a comment - Will this be back ported to the LTS 5.12.x?

            Stanislav Petr added a comment - - edited

            same issue on Jira Service Management 5.12.2

            Stanislav Petr added a comment - - edited same issue on Jira Service Management 5.12.2

              c8bcca445054 Benjamin Suess
              4bbe53f6c66f Louis (Inactive)
              Affected customers:
              13 This affects my team
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: