Version workload report

[Brian Dulin]

The version workload report only reports on Sub-tasks. Is there a way to change that to Stories or other issue types? Or, by Version, this means it only looks at Fix Versions? Our project does use versioning so is that why its not going to work for us? 

[Irina Mosina _TechTime_]

Hi @Brian Dulin 

Version Workload report works for all the issue types that have Fix Version field associated with their screen and people actually specifying it, as in allocating those issues to the version. 

So if historically you were only allocating Epics to the version (see example) then that's what you will get. 

I suggest to go to the side panel in your project, click on the Issues icon and run a quick search where you select an extra column, Fix Version and see what you got there: 

[Mary from Planyway]

Hi @Brian Dulin 

It's Mary from Planyway for Jira: workload, roadmapping, time tracking and reporting 

In Jira, the Version Workload Report is designed to help teams understand the amount of work (usually in terms of time estimated) that is associated with a particular version of their project. This report can indeed focus on specific issue types, including Sub-tasks, Stories, Bugs, Epics, etc., depending on how your Jira project and filters are set up. However, its primary function is to report on issues that are assigned to a particular "Fix Version."

Here's how it generally works and what you can do to adjust it to your needs:

Focusing on Different Issue Types

• By Default: The Version Workload Report will include all issue types that are assigned to the specified version. If it seems to only report on Sub-tasks, it might be due to the way your project or the report itself is configured.

• Adjusting Filters: To focus on Stories or other issue types, you can adjust the filter/query used for the report. This might involve specifying the issue types you're interested in. However, the direct interface of the Version Workload Report might not allow changing the issue type directly from the report settings. Instead, you would manage which issues are assigned to the version you're analyzing.

Understanding "Fix Version"

• Fix Version Usage: The "Fix Version" is a field in Jira issues that indicates which version of the project the issue is expected to be resolved in. This is how Jira tracks the workload against different versions.

• Non-Versioned Projects: If your project does not use versioning (i.e., you do not assign "Fix Version" to your issues), the Version Workload Report will not be useful. This report is inherently designed to analyze work based on project versions. Without using "Fix Version," the report cannot aggregate or display the information as intended.

Alternatives and Solutions

1. Start Using Versions: If your project could benefit from organizing work into versions, consider starting to use the "Fix Version" field. It's a powerful way to manage releases and understand the workload associated with each.

2. Custom JQL Queries: Use Jira's search with JQL (Jira Query Language) to create filters that show you the workload or issue breakdown by type for your project. You can specify the issue type, status, and other criteria.

3. Dashboard Gadgets: Instead of relying solely on the Version Workload Report, consider using other dashboard gadgets that can be configured to show data based on issue types, regardless of versioning. For instance, the "Filter Results" gadget can display issues of a specific type (like Stories) across your project.

4. Third-Party Plugins: There are numerous plugins available in the Atlassian Marketplace that extend reporting capabilities and might offer the flexibility you need like Planyway