Documentation

1. Requirements and installation

• Jira Cloud with time tracking available for the issues being reported.
• An active or evaluating Atlassian Marketplace entitlement for Version Workload Reports for Jira (VWR).
• Permission to browse the selected project, versions, saved filter, and issues in Jira.
• A current desktop browser. The VWR interface is in English.

When VWR is available in Atlassian Marketplace, a Jira or site administrator installs it through Atlassian’s ordinary app-management flow. VWR requests only read:jira-work. Atlassian manages evaluation, subscription, billing, and entitlement state.

2. Create a report

1. Open Apps → Version Workload Reports.
2. Choose Version workload, Assignee workload, or Estimate & variance.
3. Select the Jira source offered to the current user: one project and 1–50 versions, one visible project, or one accessible saved filter, as supported by that report.
4. For Version workload and Assignee workload, choose whether to include issues in Jira’s Done status category. Estimate & variance includes all status categories.
5. Run the report and review its source, status rule, timestamps, retrieval state, and estimate coverage.
6. Open issue detail to audit the rows behind the totals. Export CSV only when the result is complete.

VWR validates source identifiers on the server and builds its Jira query there. A browser request cannot supply arbitrary JQL or another user’s identity. If Jira denies a project, filter, version, or issue to the current user, VWR does not replace that denial with privileged access.

3. Calculations

• Original estimate (O) is Jira’s original estimate.
• Time spent (S) is cumulative time spent on the issue.
• Remaining estimate (R) is Jira’s current remaining estimate.
• Forecast variance is S + R − O, calculated per issue only when all three values are known.

Values remain in seconds until presentation or export and are not totalled from rounded rows. Zero is a known value. Missing, absent, invalid, or negative Jira estimate fields remain Unknown and are never silently converted to zero.

Original, spent, remaining, and variance can have different coverage. Each card and group shows known issues versus included issues. The independently covered metric cards therefore need not subtract to the sum of issue-level variance. Positive variance means spent plus remaining exceeds the original estimate; negative variance means it is below it. Variance is not a delivery-date prediction or a measure of individual productivity.

Each Jira issue ID contributes at most once, including an issue returned through several pages or selected versions. Parents and subtasks use only their own fields. Assignees are grouped by stable Jira account ID, not display name. Time spent is attributed to the issue; grouping an issue under its current assignee does not assert who logged that time.

4. CSV export

CSV is generated in the browser from the complete report already displayed. Export does not query Jira again. The file contains report, source, status, query, completeness, and unit metadata followed by issue detail and numeric hour fields.

Unknown numeric values remain blank. Unicode, quotes, separators, and line breaks are escaped. Text beginning like a spreadsheet formula is prefixed with an apostrophe. If retrieval is incomplete, totals are non-authoritative and CSV export is disabled. Once downloaded, the CSV is under the user’s and customer’s control.

5. V1 report limits

Atlassian determines billable app quantity from the applicable Jira Cloud entitlement and billing rules. Billable users are not the number of issues VWR can process in one report.

• 1–50 selected versions.
• 100 issues per Jira search page.
• 1,000 included issues per report.
• 100 pages per report.
• 18 seconds of application-side retrieval.
• At most three attempts for documented retryable Jira responses.
• Up to 1,000 visible projects, filters, or versions in a selector request.

When a limit stops retrieval, VWR marks the result incomplete, withholds authoritative totals, and disables CSV. No support above these limits is claimed for V1.

6. Troubleshooting

Confirm that the same user can open the selected project, filter, versions, and representative issues directly in Jira, then retry the report once. If it still fails, send only the diagnostic fields permitted by the VWR Support Policy.

Do not send JQL, issue text, CSV files, full API responses, credentials, tokens, or complete Forge contexts.

7. Removal and data

A Jira or site administrator removes VWR through Atlassian app management. VWR has no app-owned report, derived-state, issue-copy, preference, database, queue, or remote-backend store. It therefore has no retained customer report corpus to migrate or delete. Jira data remains in Jira under the customer’s administration, sanitized technical logs follow Atlassian’s Forge lifecycle, and CSV files already saved by a user remain under that user’s or customer’s control.

8. Supported scope and policies

The launch claim is limited to Jira Cloud, Atlassian Forge, the English VWR interface, and the documented desktop-browser experience. VWR does not claim Jira Data Center or Server, mobile, other locales, every Jira edition, screen-reader certification, or report scale above the enforced limits.

See the Privacy Policy, Data Processing Addendum, Provider-Specific Terms, and Support Policy and SLA.