Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10101

As a manager with a Kanban or Scrum Board, I want to be able to dynamically group my board by an attribute so that I may more easily organize my team's work

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • AgileBoard
    • 2
    • 7
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Being able to base Swimlanes on Stories or Assignee is simply not enough. JQL is great but what I keep hearing from managers in our company that want to use Kanban is that they want to be able to do a "group by" similar to a group by clause in SQL.

      Our biggest win would be to add Component to the "Base Swimlanes on" dropdown. Even better would be to add "Attribute" to the dropdown with a text box allowing someone to enter the attribute to group on; from there they could pick "Epic Name", Assignee, Component, etc...

            [JSWSERVER-10101] As a manager with a Kanban or Scrum Board, I want to be able to dynamically group my board by an attribute so that I may more easily organize my team's work

            Gertjan added a comment -

            I truly believe you would fix all of these related issues (see also https://jira.atlassian.com/browse/JSW-10101?jql=text%20~%20%22group%20by%20swimlanes%22)
            if you fix JSW-4669 according to the comment I wrote in JSW-10101.

            Gertjan added a comment - I truly believe you would fix all of these related issues (see also https://jira.atlassian.com/browse/JSW-10101?jql=text%20~%20%22group%20by%20swimlanes%22 ) if you fix JSW-4669 according to the comment I wrote in JSW-10101 .

            Gertjan added a comment - - edited

            I believe you guys should give people the group by option inside JQL so that they can have a dynamic option for swimlanes that can be combined with other JQL statements.
            By doing this you would close a lot of the debates about swimlanes directly.

            My team that I'm helping to setup a board is trying to get something like this (their fysical board and process is actually running smoothly like this!):
            Lane 1: "DevOps work" : showing incidents and operational work, all of this is small work and basically no EPIC link is setup for that.
            Lane 2: "Small change requests" : showing work (small stories) that need no project for it and has a wip limit to stabilize inflow of these items
            Lane 3: "Project work" : showing User stories that belong to EPICs in order to maintain a clear view on which features they are building

            In this case they would love a setup:
            Lane 1: JQL query: issueType = "Incident" AND (other filters)
            Lane 2: JQL query: issueType = "Change request" AND (other filters)
            Lane 3 till X : JQL query: issueType = "User story" group by issueType = EPIC
            Showing all EPICs per swimlane underneath the other 2 lanes. The lane names would be equal to the EPIC Name because you sorted on EPIC....
            So the work becomes nicely viewable within 1 board... + categorized like the team works...

            Just a suggestion

            Gertjan added a comment - - edited I believe you guys should give people the group by option inside JQL so that they can have a dynamic option for swimlanes that can be combined with other JQL statements. By doing this you would close a lot of the debates about swimlanes directly. My team that I'm helping to setup a board is trying to get something like this (their fysical board and process is actually running smoothly like this!): Lane 1: "DevOps work" : showing incidents and operational work, all of this is small work and basically no EPIC link is setup for that. Lane 2: "Small change requests" : showing work (small stories) that need no project for it and has a wip limit to stabilize inflow of these items Lane 3: "Project work" : showing User stories that belong to EPICs in order to maintain a clear view on which features they are building In this case they would love a setup: Lane 1: JQL query: issueType = "Incident" AND (other filters) Lane 2: JQL query: issueType = "Change request" AND (other filters) Lane 3 till X : JQL query: issueType = "User story" group by issueType = EPIC Showing all EPICs per swimlane underneath the other 2 lanes. The lane names would be equal to the EPIC Name because you sorted on EPIC.... So the work becomes nicely viewable within 1 board... + categorized like the team works... Just a suggestion

            @Jonathon Robinson , thanks for reporting this.

            BTW I did not see your vote on the ticket, You should also add your vote on the ticket and get your colleagues, team and everyone possible to get Atlassian's attention for this new feature.

            I have now added my vote and I'm going to get all my team and colleagues to do the same.

            Madhusudhan Matrubai added a comment - @Jonathon Robinson , thanks for reporting this. BTW I did not see your vote on the ticket, You should also add your vote on the ticket and get your colleagues, team and everyone possible to get Atlassian's attention for this new feature. I have now added my vote and I'm going to get all my team and colleagues to do the same.

            Many thanks for reporting this issue. We see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

            Regards,
            JIRA Agile Team

            Tom Kotecki (Inactive) added a comment - Many thanks for reporting this issue. We see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it. Regards, JIRA Agile Team

              Unassigned Unassigned
              jonarobinson Jonathon Robinson
              Votes:
              41 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated: