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

Sorting of Filter Results Gadget doesn't Work when Using More Than 3 "Order By" criteria

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

      Symptom:
      When using Filter Results Gadget, issue sorting works fine for the first three "Order By" criteria, but isn't affected by the 4th/5th/... "Order By" items. It results in the inconsistency between the issue sorting of gadget and the filter displayed when clicking on "matching issues" link at the bottom of the gadget.

      Sample:
      Filter Results Gadget shows the correct sorting for the filters with "Order By" clause less than three criteria

      assignee = currentUser() AND status in (open, "In Progress", Reopened) ORDER BY status, fixVersion, affectedVersion, component
      

      When the filter has "Order By" clause more than four criteria, Filter Results Gadget applies the first three ones and ignores others after 3rd one.

      assignee = currentUser() AND status in (open, "In Progress", Reopened) ORDER BY status, fixVersion, affectedVersion, component
      

            [JRASERVER-21443] Sorting of Filter Results Gadget doesn't Work when Using More Than 3 "Order By" criteria

            Ah I see thanks.

            Patrick Fletcher added a comment - Ah I see thanks.

            This has only been resolved for the server versions, not the cloud version :/

            iSOFT Systems added a comment - This has only been resolved for the server versions, not the cloud version :/

            Why is this marked RESOLVED when it is still a problem? If ORDER BY is defined its for a reason.

            Patrick Fletcher added a comment - Why is this marked RESOLVED when it is still a problem? If ORDER BY is defined its for a reason.

            Sorting also appears to be broken for the Filter Results Gadget when using 3 sort criteria (total 27 characters). Please update the title of this bug to read: "Sorting of Filter Results Gadget doesn't Work when Using More Than 2 'Order By' criteria".

            As Sorting is core functionality of a dashboard, I request upgrading the priority to Critical to prevent the starvation on this issue that has been occurring since 2010.

            Andrew Hammond added a comment - Sorting also appears to be broken for the Filter Results Gadget when using 3 sort criteria (total 27 characters). Please update the title of this bug to read: "Sorting of Filter Results Gadget doesn't Work when Using More Than 2 'Order By' criteria". As Sorting is core functionality of a dashboard, I request upgrading the priority to Critical to prevent the starvation on this issue that has been occurring since 2010.

            Is there any workaround for this bug? Probably not.

            Miroslav Brabenec added a comment - Is there any workaround for this bug? Probably not.

            Harald Rätscher added a comment - - edited

            Awaiting fix too and still can not believe how project leads, who strongly use dashboards, can work without this feature, because the overview feature of the dashboard is totally wrecked and you always have to consult the original filter. So as a consequence, the filter gadget is useless in this case. And I am still wondering, why having more than 3 sorting criteria is really so uncommon.

            For me "ORDER BY duedate ASC, priority DESC, type ASC, status DESC, updated DESC" totally makes sense, at least the first four.

            Thank you in advance!

            Harald Rätscher added a comment - - edited Awaiting fix too and still can not believe how project leads, who strongly use dashboards, can work without this feature, because the overview feature of the dashboard is totally wrecked and you always have to consult the original filter. So as a consequence, the filter gadget is useless in this case. And I am still wondering, why having more than 3 sorting criteria is really so uncommon. For me "ORDER BY duedate ASC, priority DESC, type ASC, status DESC, updated DESC" totally makes sense, at least the first four. Thank you in advance!

            Still an issue in v7.1. Can't wait until this bug gets fixed! Thanks

            Brian Gaudreault added a comment - Still an issue in v7.1. Can't wait until this bug gets fixed! Thanks

            Yes harald.raetscher, the bug report is clear at the moment. As you mention, you can always refer back to the original filter in the issue navigator to obtain correctly sorted results as a workaround in the meantime.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Yes harald.raetscher , the bug report is clear at the moment. As you mention, you can always refer back to the original filter in the issue navigator to obtain correctly sorted results as a workaround in the meantime. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            This sounds good From my perspective this is no big deal. The filter already selects the issues to be display and normally has some order criteria. And a gadget on top shall only provide some kind of view, to narrow the information. So I think it makes no sense to allow the user to select from all the fields, because only the fields from the filter should be available. As a consequence, there is no problem with the sorting, because it will be obtained from the filter itself.

            Am I thinking in the wrong direction?

            Harald Rätscher added a comment - This sounds good From my perspective this is no big deal. The filter already selects the issues to be display and normally has some order criteria. And a gadget on top shall only provide some kind of view, to narrow the information. So I think it makes no sense to allow the user to select from all the fields, because only the fields from the filter should be available. As a consequence, there is no problem with the sorting, because it will be obtained from the filter itself. Am I thinking in the wrong direction?

            Hi harald.raetscher,

            We determine priority strictly based on the information available at Priority Levels.

            To further clarify, the priority field in this project is used to measure an issue's severity rather than its scheduling priority. Having said this, this is an issue that I have been monitoring closely for a while and given we have freed up some space in our backlog and the number of votes and interest on this issue, I have just added it to my team's short-mid term backlog.

            Please do watch the issue for further information, we will update its status as soon as more information is available.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi harald.raetscher , We determine priority strictly based on the information available at Priority Levels . To further clarify, the priority field in this project is used to measure an issue's severity rather than its scheduling priority. Having said this, this is an issue that I have been monitoring closely for a while and given we have freed up some space in our backlog and the number of votes and interest on this issue, I have just added it to my team's short-mid term backlog. Please do watch the issue for further information, we will update its status as soon as more information is available. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

              tkanafa Tomasz Kanafa
              kren Kelson Ren
              Affected customers:
              23 This affects my team
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: