Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-4831

Sort order for Ext ID column for Stories and Features in incorrect

XMLWordPrintable

    • 1
    • Severity 3 - Minor
    • No

      Issue Summary

      Customer has noticed that list views containing the External ID (Ext ID field) for Jira (Stories and Features) don't sort correctly on the numeric part of the ID. As the data within the Ext ID field is alphanumneric, the sort order is based on just looking at each character   in order.

      An example of current behaviour (undesirable) might be

       ID-1
       ID-101
       ID-11
       ID-12
       ID-2
       ID-22
       ID-200
       ID-30
       ID-3000
       ID-5
      
      

      Where the correct / desired behaviour would be: 

      ID-1
      ID-2
      ID-5
      ID-11
      ID-12
      ID-22
      ID-30
      ID-101
      ID-200
      ID-3000
      

      The desired type of sort is sometimes known as a Natural Search

      Apparently this issue was fixed (at least for Features/requestgrid.asp  but possibly not for stories/storygrid.asp) in a previous JAC ticket and has resurfaced

      https://jira.atlassian.com/browse/JIRAALIGN-2340

      Steps to Reproduce

      1. Create more than 100 stories/features in a Jira integrated Project
      2. Enable visibility of Ext  ID in Jira Align and
      3. Attempt to sort on the column in Team > Stories (storygrid.asp) or Program > Features (requestfrid.asp)
      4. observe that sorting is done agajnst the first digit of the numeric part of the string followed by the second digit instead of treating the numeric part as one number

      Expected Results

      ID-1
      ID-2
      ID-5
      ID-11
      ID-12
      ID-22
      ID-30
      ID-101
      ID-200
      ID-3000
      

       

      Actual Results

      ID-1
      ID-101
      ID-11
      ID-12
      ID-2
      ID-22
      ID-200
      ID-30
      ID-3000
      ID-5
      

      Workaround

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

            dfuller@atlassian.com Don Fuller
            1b00672850a3 Colin Weaver
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: