Version Workload Reports for Jira Cloud

See workload, coverage, and variance without rebuilding spreadsheets.

For project, engineering, and delivery managers who plan in hours and need to understand the estimates already held in Jira.

Version Workload Reports is available on the Atlassian Marketplace for Jira Cloud.

Forge hostedJira CloudRead-only user access

Plan from the estimates already in Jira.

Choose a project and versions, a whole project, or an accessible saved filter. VWR reports known hours together with coverage, links every total to its contributing issues, and exports the exact complete result to CSV.

Read why known hours still need estimate coverage

Three focused reports, with the detail behind every total.

These approved product views use controlled synthetic data. Start by choosing the report and Jira scope, read workload with honest estimate coverage, then inspect the contributing issues and export a complete result.

Version Workload Reports showing its three report choices, a synthetic QA project, two selected versions, and a complete result.
1. Choose the right workload view. Select Version workload, Assignee workload, or Estimate & variance, then use the project, versions, or saved filters available to the signed-in user.
2. Read hours with honest estimate coverage
Complete version workload report with hour metrics, known-issue coverage, unassigned flags, and anonymized grouping rows.
2. Read hours with honest coverage. Compare remaining, original, spent, and variance hours while seeing how many Jira issues have a known value for each metric.
3. Verify issue detail and export the result
Complete report with the Export CSV control and anonymized issue detail showing representative rows and estimate fields.
3. Verify detail and export. Audit the rows behind the totals, distinguish a missing estimate from zero, and export only when Jira retrieval completed successfully.

Visible issue keys and summaries are synthetic. Personal labels are presentation-anonymized; the displayed numbers and report states were not changed.

Install, choose a scope, and inspect the result.

Installation from Atlassian Marketplace

A Jira or site administrator can open VWR on Atlassian Marketplace, choose the available evaluation or install action, select the Jira Cloud site, review the requested read permission, and complete the installation. Users need Jira access to the projects, versions, filters, and issues they report on.

Where to find it

In Jira, open Apps and select Version Workload Reports.

Create a report in six steps

  1. Choose a report. Use Version workload, Assignee workload, or Estimate & variance for the decision you need to make.
  2. Select the source. Pick the project, versions, or saved filter that Jira makes available to your account.
  3. Choose the status rule. Workload reports exclude Jira’s Done status category by default; you can include it when needed.
  4. Run the report. Review its source, timestamps, retrieval state, issue count, and estimate coverage before using the totals.
  5. Open issue detail. Audit the Jira rows that contributed to the result and see which values are known or missing.
  6. Export when complete. Download CSV from the result already displayed; incomplete retrieval cannot be exported.

Version workload

See remaining hours by current assignee and issue type across one project and 1–50 selected versions.

Assignee workload

Compare remaining hours and estimate coverage for a whole project or an accessible saved filter.

Estimate & variance

Review original, spent, remaining, and forecast-variance hours for a project or accessible saved filter.

Jira permissions respected

Interactive reads use the signed-in user, with no privileged fallback.

Unknown stays unknown

Missing estimates are never silently converted to zero or complete coverage.

Complete results only

Incomplete retrieval is marked non-authoritative and cannot be exported.

No app-owned report store

Reports stay in the browser session; CSV is generated from the displayed result.

Version Workload Reports FAQ

Does Version Workload Reports change Jira issues?

No. VWR is read-only. It does not create, edit, transition, or delete issues, and it does not modify project configuration.

Can VWR show Jira data a user cannot already access?

No. Interactive Jira reads use the signed-in user’s permissions. Projects, versions, filters, and issues that Jira does not return to that user are not intentionally exposed through the app.

Are missing estimates treated as zero?

No. Zero is a known value; a missing or invalid estimate remains unknown. Each metric shows its known-issue coverage so an incomplete estimate population is visible.

How is forecast variance calculated?

For an issue with all three values known, variance is time spent plus remaining estimate minus original estimate. The total uses only that complete-component subset. It is not a delivery-date prediction or a measure of individual productivity.

Does CSV export run another Jira query?

No. The browser generates CSV from the complete report already displayed. Export is disabled when retrieval is incomplete, and unknown numeric values remain blank.

Are billing size and report size the same thing?

No. Atlassian Marketplace manages the site’s evaluation, subscription, and billing. VWR separately limits a report to 1,000 included issues, 100 pages, and up to 50 selected versions.

Read the complete Version Workload Reports documentation

Clear before you install.