Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-5104

Add grouping/swimlanes/assignee summary to Plan Mode

    XMLWordPrintable

Details

    • Suggestion
    • Status: Closed (View Workflow)
    • 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.

    Description

      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

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: