• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • AgileBoard
    • None
    • 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.

      The work mode offers the possibility to add swimlanes on a per-user basis - this allows us to easily see who's buried in work and who's twiddling their thumbs, waiting for stuff to do.

      The plan mode however does not allow us to group things like that. Theres the fancy Sprint bar that allows us to add issues to the next sprint, but we don't know if the added issues (lets say, 40 in total) are distributed evenly (about 4 per dev, with 10 devs) unless we actually start the sprint and switch to the plan mode.

      Right now, we use the Planning Board (not the Rapid Board) in Assignee View to pick issues and assign them to a Release Version (<product version>.<sprint>, like 6.0.0.5 for the 5th sprint of version 6.0.0), trying to achieve an evenly distributed work load for each user.
      Then we switch to the Rapid Board, define a Quick Filter for that particular version (again, 6.0.0.5 for the example) and apply it to the Plan Mode.
      From there, its the same as just adding issues to a new sprint - but I guess the Plan Mode could do a lot better than that

            [JSWSERVER-5104] Add grouping/swimlanes/assignee summary to Plan Mode

            Many thanks for reporting this issue. I'm resolving this issue as a duplicate of the linked issue, as the functionality requested will be covered there. Please watch that issue for updates.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Many thanks for reporting this issue. I'm resolving this issue as a duplicate of the linked issue, as the functionality requested will be covered there. Please watch that issue for updates. Regards, JIRA Agile Team

            Renato Atilio added a comment - - edited

            I have a custom field for Customer(s). Creating an Epic for each Customer isn't a feasible option, so I can't see us using the Plan mode the way it is currently as well.

            Thinking further, the swimlanes for a Plan mode might not be the best solution, considering the high amount of issues to rank, and really an Epic-like solution for "custom fields" would be awesome.

            Renato Atilio added a comment - - edited I have a custom field for Customer(s). Creating an Epic for each Customer isn't a feasible option, so I can't see us using the Plan mode the way it is currently as well. Thinking further, the swimlanes for a Plan mode might not be the best solution, considering the high amount of issues to rank, and really an Epic-like solution for "custom fields" would be awesome.

            Right on the spot! If that were to work for assignees, we'd certainly be able to (finally) move to the rapid board.
            Components, Projects of-course and Labels would be the icing on the cake for our case, but certainly a must if you consider other teams and methods of dealing with such things.

            Emanuel Wlaschitz added a comment - Right on the spot! If that were to work for assignees, we'd certainly be able to (finally) move to the rapid board. Components, Projects of-course and Labels would be the icing on the cake for our case, but certainly a must if you consider other teams and methods of dealing with such things.

            Here's what I think they should do. Look at this rapid board. https://jira.atlassian.com/secure/RapidBoard.jspa?rapidView=96&view=planning. Notice how they've implemented Epics. I think they should build on this and have something similar for Assignees and also Components, and possibly Labels. I think this would solve all our problems.

            Mark DeMichele added a comment - Here's what I think they should do. Look at this rapid board. https://jira.atlassian.com/secure/RapidBoard.jspa?rapidView=96&view=planning . Notice how they've implemented Epics. I think they should build on this and have something similar for Assignees and also Components, and possibly Labels. I think this would solve all our problems.

            After a semi-long discussion with my colleague (started by the innocent question "why aren't we using the rapid board again?") I decided to throw together a quick mockup that may present a potential solution to this.

            Right now, the Plan Mode shows a short "How to" on the right-hand side (top part of the mockup), while selecting an issues shows details for that particular issue (bottom part).

            Whats kind-of missing is the middle part of the mockup, which shows some sort of summary for the selected sprint - this should be similar to the classic Planning Board view and list issues by type and/or by assignee (maybe configurable to use an aggregated time estimate, story points, or simply the amount of issues per assignee).
            As alternative, I could also imagine having a merged view of top and middle parts, where the Plan Mode introduction is replaced with the first upcoming sprint summary (at least for our cases, we may start planning a second sprint to follow, but it really gets interresting to see the workload once it becomes the next upcoming sprint).

            Emanuel Wlaschitz added a comment - After a semi-long discussion with my colleague (started by the innocent question "why aren't we using the rapid board again?") I decided to throw together a quick mockup that may present a potential solution to this. Right now, the Plan Mode shows a short "How to" on the right-hand side (top part of the mockup), while selecting an issues shows details for that particular issue (bottom part). Whats kind-of missing is the middle part of the mockup, which shows some sort of summary for the selected sprint - this should be similar to the classic Planning Board view and list issues by type and/or by assignee (maybe configurable to use an aggregated time estimate, story points, or simply the amount of issues per assignee). As alternative, I could also imagine having a merged view of top and middle parts, where the Plan Mode introduction is replaced with the first upcoming sprint summary (at least for our cases, we may start planning a second sprint to follow, but it really gets interresting to see the workload once it becomes the next upcoming sprint).

            We too have a need to be able to see workload by assignee in plan mode. Our only current option is to create a quick filter for each team member

            Jeremy Pamplin added a comment - We too have a need to be able to see workload by assignee in plan mode. Our only current option is to create a quick filter for each team member

            Another idea on this:
            The right side of Plan Mode currently shows the steps on what to do here. I'm pretty sure this thing could be moved elsewhere, and be replaced with some sort of summary view.
            It could, for example, list all Assignees (or Components) along with the amount of issues (or the sum of estimated time, the sum of story points/business value, etc) as quick indication of how issues are distributed in the ready-to-start sprint.

            Emanuel Wlaschitz added a comment - Another idea on this: The right side of Plan Mode currently shows the steps on what to do here. I'm pretty sure this thing could be moved elsewhere, and be replaced with some sort of summary view. It could, for example, list all Assignees (or Components) along with the amount of issues (or the sum of estimated time, the sum of story points/business value, etc) as quick indication of how issues are distributed in the ready-to-start sprint.

            Aww, and then we thought this is gonna work.
            The last line above unfortunately doesnt always work that well. We just had the case that more issues were around than issues assigned to the version. The Quick Filter hides them, but they are still added to the sprint. Only resetting them afterwards using Bulk edit on the Sprint Field does the trick in such cases, so a built-in solution to the Rapid Board would be really great.

            Emanuel Wlaschitz added a comment - Aww, and then we thought this is gonna work. The last line above unfortunately doesnt always work that well. We just had the case that more issues were around than issues assigned to the version. The Quick Filter hides them, but they are still added to the sprint. Only resetting them afterwards using Bulk edit on the Sprint Field does the trick in such cases, so a built-in solution to the Rapid Board would be really great.

              Unassigned Unassigned
              e1e73c45da94 Emanuel Wlaschitz
              Votes:
              22 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: