Documentation
Worklog Hours Summary for Jira
Jira Cloud teams with hours billed by epic/component cannot get a summarized, exportable report of worklog hours grouped by epic or component. Existing apps have outages and weak search, so the job cannot be done reliably today.
Overview
Jira Cloud teams with hours billed by epic/component cannot get a summarized, exportable report of worklog hours grouped by epic or component. Existing apps have outages and weak search, so the job cannot be done reliably today.
Key Features
- A user can select a project and date range, toggle grouping between epic and component, and the displayed totals update without a page reload.
- The CSV export contains exactly the rows in the displayed table, and for an instance with 5,000 worklogs across pages, all rows are included with no truncation.
- A request from tenant A cannot retrieve, export, or cache worklogs from tenant B via direct URL, API, or shared storage; the app only calls the authenticated tenant's Jira REST API.
- If the epic-link custom field is absent or hidden, the app shows the tenant-specific field configuration instead of failing silently.
- When Jira returns HTTP 429, the app retries with exponential backoff and displays a progress indicator; the report eventually completes or shows an error with a retry button.
Getting Started
Install the app into your Jira instance from the Atlassian Marketplace.
Stuck
Ask a person.
If this guide does not answer your question, email us and a human answers. Name the product, what you were doing, and what happened instead. That is genuinely all we need to start.