Hours logged per release in Jira
Jira Cloud, worklogs and releases. The figures from our demo site on 10 and 12 November 2026.
Hours logged tell you where the time went. They do not tell you which release that time shipped in. This page says what Jira shows by itself, then reads one epic’s hours with Logline and the releases they went into with Changeline.
What Jira does by itself
- One total per work item. A work item’s Time Tracking field adds up its worklogs. It shows no split by week, so the hours that went into an epic’s done work are a sum you make by hand.
- A release is a fix version. A work item names the release it shipped in under Fix versions, one work item at a time. Jira has no field that adds up an epic’s logged hours by release.
- No release in the time report. A worklog says when the time was logged and by whom, not which release the work went into.
One epic, two answers
Changeline is our app. So is Logline. Both read what Jira already holds, and Changeline only reads Jira and changes nothing in it. The example is One-page checkout, an epic in our demo’s Checkout space, and the hours are the worklogs of its work items from 2 to 10 November.
Where the hours went, with Logline

- 80h on one epic. Logline sums the worklogs of its work items: 70h in the week of 2 November, 10h in the part week after it.
- The biggest share went to a shipped item. CHK-28, Delivery date picker, took 18h, against an estimate of 16h, and shipped in release 1.7.
- The hours are one account’s. In this demo every worklog is logged by the same account, so the report has no people to compare. A team’s own worklogs show each person’s row.
Logline is on the Atlassian Marketplace; its page on lineset.dev has more.
Which release they shipped in, with Changeline
The picture under this page is Changeline’s Releases tab, the failed releases first, release 1.7 opened. Changeline lists each release with its work items, so the hours a work item took are read against the release it went into. Release 1.7 has five work items, and CHK-34 and CHK-140 are failures against it. Changeline counts a release once it is marked Released, and Failures and recovery time explains how a failure points at one, and Epic progress before a release in Jira reads the same epic’s totals. Back to Changeline.
DORA here is the research programme at Google behind deployment frequency and three other keys, not the EU’s Digital Operational Resilience Act. DORA is a trademark of Google LLC, and Changeline is not made or endorsed by Google.
