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

      From a chat with an existing JIRA customer:

      They'd love to have a chart showing number of hours per developer per iteration. Similar to the existing version workload report in JIRA, but with:

      1. Nice graphics
      2. The ability to drag n drop issues from one developer to another to balance the allocated workload.

          Form Name

            [JSWSERVER-1316] Chart showing workload by developer

            Duplicate of GHS-1333

            Stuart Bargon [Atlassian] added a comment - Duplicate of GHS-1333

            @Oliver, you can already set a capacity per developer inside Greenhopper in the Asignee Board.

            What we are missing is the ability to see a graph of that capacity together with the burndown graph. I think i will create an issue on that.

            Deleted Account (Inactive) added a comment - @Oliver, you can already set a capacity per developer inside Greenhopper in the Asignee Board. What we are missing is the ability to see a graph of that capacity together with the burndown graph. I think i will create an issue on that.

            Find attached a quick UI-Mockup to convey the general idea...

            Would be nice to have a limit (capacity) per developer (red line or similar) to illustrate how many issues a developer can realistically tackle within one iteration, but this would require another user input for each developer (available hours)...

            Oliver Nölle added a comment - Find attached a quick UI-Mockup to convey the general idea... Would be nice to have a limit (capacity) per developer (red line or similar) to illustrate how many issues a developer can realistically tackle within one iteration, but this would require another user input for each developer (available hours)...

              Unassigned Unassigned
              doflynn David O'Flynn [Atlassian]
              Votes:
              3 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: