• 6
    • 16
    • 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.

      As a Project Administrator I would like the ability to generate a Sprint Workload Report similar to the Version Workload Report from JIRA.

      The Version Workload Report displays time tracking information on the current workload for a specific version within a specific project.
      For the specified version, it shows a list of unresolved issues assigned to each user, each user's workload, and a summary of the total workload remaining for the version.

            [JSWSERVER-5849] Sprint Workload Report

            Hi!
            You can try Time in Status for Jira add-on. There was a recent release of the Sprint Perfomance Report feature. There are charts and diagrams on the sprint structure, velocity, workload, completion rate, scope change, etc. You can view this report only on boards where sprints are enabled. 

            Valeriia_Havrylenko_SaaSJet added a comment - - edited Hi! You can try Time in Status for Jira add-on . There was a recent release of the Sprint Perfomance Report feature. There are charts and diagrams on the sprint structure, velocity, workload, completion rate, scope change, etc. You can view this report only on boards where sprints are enabled. 

            Has this report been resolved, as a PM/SM this is an essential report.

            kusay ahmed added a comment - Has this report been resolved, as a PM/SM this is an essential report.

            If someone decides to create this report in Excel, the app called Better Excel Plugin can export the worklogs with all their details (who, when, how much work, on what issue, etc.).

            Then it can create the sub-reports (Summary and Individual Estimates) as pivot tables from this data.

            There is even a template called worklog-report.xlsx that delivers similar aggregations and that can be fed with a JQL like "sprint = <your sprint here>". (You can, of course, customize that to your needs.) See here: samples.

            (Diclr: this is a paid and supported app. I am a developer working on this.)

            Aron Gombas [Midori] added a comment - If someone decides to create this report in Excel, the app called Better Excel Plugin can export the worklogs with all their details (who, when, how much work, on what issue, etc.). Then it can create the sub-reports ( Summary and Individual Estimates ) as pivot tables from this data. There is even a template called worklog-report.xlsx that delivers similar aggregations and that can be fed with a JQL like "sprint = <your sprint here>". (You can, of course, customize that to your needs.) See here: samples . (Diclr: this is a paid and supported app. I am a developer working on this.)

            Vicky Craig added a comment - - edited

            Can the storypoints be added? Chart for the number of storypoints per user per sprint?

            Vicky Craig added a comment - - edited Can the storypoints be added? Chart for the number of storypoints per user per sprint?

            as far as i know you can only work with addon or exporting information (or using reporting inside jira but mean other plugin as well)

            • Script runner and create a calculated filed about remaining estimate
            • BI and reporting tool: Eazy bi, dataplane, connection directly to db or other solution (excel, qlikview etc)
            • plugin more dedicated about forecast and planning/progress. Tempo planner, portfolio, biggant ....etc etc etc.

            This is not something accetpable for a lot of customers, but actually burndown (that can help you to understand the situation) doesn't have any kind of

            • filter for issuetype, version or more
            • capacity check for people
            • progress considering going deep and splitting information for resources or team and more.

            Fabrizio Galletti added a comment - as far as i know you can only work with addon or exporting information (or using reporting inside jira but mean other plugin as well) Script runner and create a calculated filed about remaining estimate BI and reporting tool: Eazy bi, dataplane, connection directly to db or other solution (excel, qlikview etc) plugin more dedicated about forecast and planning/progress. Tempo planner, portfolio, biggant ....etc etc etc. This is not something accetpable for a lot of customers, but actually burndown (that can help you to understand the situation) doesn't have any kind of filter for issuetype, version or more capacity check for people progress considering going deep and splitting information for resources or team and more.

            Is there an update on this? Seems obvious that anyone using JIRA for agile project management need to get a resource allocation overview to make sure that the sprint scope is balanced.

            Anders Brogestam added a comment - Is there an update on this? Seems obvious that anyone using JIRA for agile project management need to get a resource allocation overview to make sure that the sprint scope is balanced.

            Having the possibility to track sprint workload is an absolute necessity and it is a real deal breaker for us that this is not possible. Seems to me that there is an systemic
            failure from Atlassian to understand software development, and the customers need. The original estimate is basically useless once a sprint is started. This requirement of having an overview of remaining work must be totally obvious for anyone which has ever worked with scrum.

            The lack of this feature is bade enough, but what is even worse is that it demonstrate that Atlassian does not understand how SW development. This adds to the list of unpleasant surprises after spending 1800$ USD on a issue tracker, i cannot help but wonder what will be the next unpleasant surprise.

            Per Thomas Hille added a comment - Having the possibility to track sprint workload is an absolute necessity and it is a real deal breaker for us that this is not possible. Seems to me that there is an systemic failure from Atlassian to understand software development, and the customers need. The original estimate is basically useless once a sprint is started. This requirement of having an overview of remaining work must be totally obvious for anyone which has ever worked with scrum. The lack of this feature is bade enough, but what is even worse is that it demonstrate that Atlassian does not understand how SW development. This adds to the list of unpleasant surprises after spending 1800$ USD on a issue tracker, i cannot help but wonder what will be the next unpleasant surprise.

            Hi everyone,

            We in Tempo use remaining estimates a lot and Tempo Planner has a dedicated view to see the workload in the sprint by team member. If you like to see what it looks like, check the image in the docs. How it works is that Planner calculates the capacity of the team members and uses the remaining estimates to calculate individual and team workload.

            Cheers,
            Vidar (Tempo)

            Viðar Svansson [Tempo] added a comment - Hi everyone, We in Tempo use remaining estimates a lot and Tempo Planner has a dedicated view to see the workload in the sprint by team member. If you like to see what it looks like, check the image in the docs . How it works is that Planner calculates the capacity of the team members and uses the remaining estimates to calculate individual and team workload. Cheers, Vidar (Tempo)

            Honestly, while the new workload summary is nice, just giving us a "Workload Report" which can summarize by a filter (rather than just a "Version") would be even better. I agree with the above comments - remaining time is required - but the Workload Report also allows for "Sub-task inclusion", which is hugely important to understand where the workload is assigned.

            Jordan Paul added a comment - Honestly, while the new workload summary is nice, just giving us a "Workload Report" which can summarize by a filter (rather than just a "Version") would be even better. I agree with the above comments - remaining time is required - but the Workload Report also allows for "Sub-task inclusion", which is hugely important to understand where the workload is assigned.

            I agree as well - three columns of Original Time Estimate, Time Spent and Remaining Time Estimate would be great with the top priority being on Remaining Time Estimate.

            John Garrett added a comment - I agree as well - three columns of Original Time Estimate, Time Spent and Remaining Time Estimate would be great with the top priority being on Remaining Time Estimate.

              Unassigned Unassigned
              tribeiro Thiago Ribeiro
              Votes:
              154 Vote for this issue
              Watchers:
              93 Start watching this issue

                Created:
                Updated: