Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JQL
    • Labels:
      None
    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      Say for example I need to search the issues in a specific project and group them by their Priority and get the count of each Priority issues for each User..

      user1 (Total :15 issues)(Priority 1 : 5 issues )(Priority 2: 10 issues)
      user1 (Total : 5 issues)(Priority 1 : 1 issues )(Priority 2: 4 issues)

        Attachments

          Issue Links

            Activity

            Hide
            ferenc.kiss Ferenc Kiss [Midori] added a comment -

            Grouping and aggregation is simply not in the scope of JQL. Regarding the SQL analogue, JQL merely focuses on the "WHERE" clause.

            You can, however, export the JQL results (issues) into smart Excel spreadsheets, for further data analysis with the Better Excel Plugin.
            What you describe is particularly easy to implement as an Excel pivot table (dimensions: assignee, priority and then use the "count" metric in the body cells).

            Show
            ferenc.kiss Ferenc Kiss [Midori] added a comment - Grouping and aggregation is simply not in the scope of JQL. Regarding the SQL analogue, JQL merely focuses on the "WHERE" clause. You can, however, export the JQL results (issues) into smart Excel spreadsheets, for further data analysis with the Better Excel Plugin . What you describe is particularly easy to implement as an Excel pivot table (dimensions: assignee, priority and then use the "count" metric in the body cells).
            Hide
            benny.tordrup217690321 Benny Tordrup added a comment -

            When in general working with the Issue navigator, I see a great potential to be able to group the issues found in some way - for example by project in a "Assigned to me" filter when working on multiple projects and having issues assign on all projects. Potentially also with the ability in the Issue navigator to collapse based on the group by value.

            Show
            benny.tordrup217690321 Benny Tordrup added a comment - When in general working with the Issue navigator, I see a great potential to be able to group the issues found in some way - for example by project in a "Assigned to me" filter when working on multiple projects and having issues assign on all projects. Potentially also with the ability in the Issue navigator to collapse based on the group by value.
            Hide
            e.lasman Yevgen Lasman added a comment -

            @Ferenc Kiss [Midori] mentioned good idea, unless you have more than 1000 issues to work on. 12,3K in my case.

            Show
            e.lasman Yevgen Lasman added a comment - @Ferenc Kiss [Midori] mentioned good idea, unless you have more than 1000 issues to work on. 12,3K in my case.
            Hide
            ferenc.kiss Ferenc Kiss [Midori] added a comment -

            @Yevgen If you are worried about the 1000 issue limit, you can lift that any time as explain here.

            The limits set up according to that article applies to all built-in and 3rd party exports, including the Better Excel Plugin.

            Show
            ferenc.kiss Ferenc Kiss [Midori] added a comment - @Yevgen If you are worried about the 1000 issue limit, you can lift that any time as explain here . The limits set up according to that article applies to all built-in and 3rd party exports, including the Better Excel Plugin.
            Hide
            e.lasman Yevgen Lasman added a comment - - edited

            Well, there is no better way to spoil whole instance than to "fine tune" limits And while there is a workaround, yet at the edge of "dirty hack", I still think GROUP BY could be a helpful addition; as well as LIMIT.

            Show
            e.lasman Yevgen Lasman added a comment - - edited Well, there is no better way to spoil whole instance than to "fine tune" limits And while there is a workaround, yet at the edge of "dirty hack", I still think GROUP BY could be a helpful addition; as well as LIMIT.

              People

              • Assignee:
                Unassigned
                Reporter:
                jalbion Janet Albion [Atlassian]
              • Votes:
                2 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: