Documentation for JIRA 6.4 (This documentation includes the project navigation sidebar). Not using this? See below:
(JIRA 6.4 without sidebar documentation | JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

The Version Workload Report displays useful 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.

Note: this report is only available if time tracking has been enabled by your JIRA administrator.


On this page:

What does the Version Workload report look like?

The report generated will look something like this:

Screenshot: Version Workload Report

The first table summarises the workload for each user, broken down by issue type, for the specified version.

Following the summary, the report is composed of individual sections for each user --- with workload broken down by issue type. Each individual section begins with the workload total for the specific user. Finally, all unassigned issues (if any exist) are displayed.

Generating a Version Workload Report

To generate the report:

  1. Navigate to the desired project.
  2. Choose Summary (tab) > Reports section > Version Workload Report.
  3. In the Version drop-down list, select the version on which you wish to report. The report will include all issues that belong to this version, that is, all issues whose Fix Version is this version.
  4. In the Display unestimated issues drop-down list, choose which issues will be included in the report:
    • Select Yes to show all unresolved issues, regardless of the value of their Estimated Time Remaining or Original Estimate fields.
    • Select No to exclude issues which are not time-tracked (i.e. do not have an Original Estimate specified).
  5. In the Sub-task Inclusion drop-down list (note, this will only appear if sub-tasksare enabled), choose which sub-tasks will be included in the report, for all parent issues that belong to this version:
    • Select Only include sub-tasks with the selected version to only include an issue's sub-tasks if the sub-tasks belong to the same version as the issue; or
    • Select Also include sub-tasks without a version set to include an issue's sub-tasks if the sub-tasks belong to either the same version as the issue or to no version; or
    • Select Include all sub-tasks to include all of an issue's sub-tasks, regardless of whether the sub-tasks belong to the same version, some other version or no version.

Note: sub-tasks which belong to this version, but whose parent issues do not belong to this version, will always be included in the report.

  • No labels

8 Comments

  1. Anonymous

    Hello,

     

    It should be nice to be able to do it on multiple version.

    for example I want to know the workload of all my incoming release of 5 : 5.0 5.1 and 5.2

     

    morgan

  2. Anonymous

    Is there a way to easily filter this for only certain resources on a project?

  3. Note JRA-13622 "The Version Workload report shows unresolved issues only."

    That means if your work flow allows resolved issues to include remaining time (e.g. for review or confirmation of the resolution) they won't be included in the report and the "summary of the total workload remaining for the version" won't be the same as the total remaining time for all issues in the version, as reported for example by the Time Tracking Report, or GreenHopper.

    See JRA-13729 to vote for an improvement to include options for showing Resolved/Unresolved and Complete/Incomplete issues in these reports.

  4. This report is good but is lacking in that it does not take into account parallel execution by users.

    For example, suppose we have the following data:

    UserEstimate
    User A1 week
    User B3 day
    TOTAL1 week, 3 day

    The Total is simply summing the effort required (thus User A + User B = 1 week + 3 day) but in terms of duration, the figure of 1 week is not called out.

    Perhaps a useful enhancement would be to display the effort and duration totals and then permit customization of parallel execution.  For example, in some instances two tasks might be independent and thus could be completed in parallel, whereas in other cases they may be dependent and thus must be performed consecutively.

    Could the consecutive vs concurrent angle be covered by the Issue Link field, in which JIRA users can indicate dependencies between Issues?

     

     

  5. Anonymous

    Hello,

    Is there a way to show the report with the JQL: earliestUnreleasedVersion? For issues this works and i like to do this also for the workload report.

  6. Anonymous

    Hi everyone,

    If you are using JIRA Agile it would be needed to filter the report to a certain sprint, too. This would help in the sprint planning meeting to check the workload for each developer.

    HJ

  7. Is it possible to create this report across multiple projects?

    1. Hi Mark,

      At this time it's not possible to run the report across multiple projects. We have had requests to change the report to give it more functionality. One such request is here:  JRA-31075 - Workload report based in a filter Open  You can vote for these issues and we'll try get to them as soon as we can!

      Thanks again for the feedback!

      Warren