Skip to content
Menu
HelpWho has time for the next release in Jira

Who has time for the next release in Jira

Jira Cloud, estimates, due dates and releases. The figures from our demo site on 10 and 12 November 2026.

An unreleased version holds work with estimates and due dates, and a release is only as soon as the people on that work have the hours. Jira shows each person’s open estimates as one total, not against the weeks they have. This page says what Jira shows by itself, then reads one epic’s next release with Workline and the pace the team has shipped at with Changeline.

What Jira does by itself

  • One total, no weeks. A search lists the open work items with their assignee and remaining estimate, as one total. Sixty hours due this week and sixty hours spread over a month look the same.
  • One working day for the site. Jira’s time tracking settings give one working day and week for the whole site, with nothing for a holiday or a part-time colleague.
  • No pace. Jira does not say how long work took to reach a release, so the time a planned item will need is an estimate you make from past releases by hand.

One epic, two answers

Changeline is our app. So is Workline. 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, with six open child work items for the unreleased version Checkout 2.0.

Who has the time, with Workline

Workline’s plan over the Checkout space by epic: 2 epics, planned from 5 work items at 8h a day Monday to Friday, the epic CHK-62 One-page checkout opened with 54h this week and 24h the week after, and under it one person’s row opened to their work items, 46h this week against their 40h week.
Workline’s plan over the Checkout space by epic: 2 epics, planned from 5 work items at 8h a day Monday to Friday, the epic CHK-62 One-page checkout opened with 54h this week and 24h the week after, and under it one person’s row opened to their work items, 46h this week against their 40h week.
  • 54h of the epic this week, 24h the week after. Workline spreads each open item’s remaining estimate over the working days until its due date, at the plan’s 8 hours a day, Monday to Friday.
  • One person over. One person’s row holds 46h this week against their 40h, and the row is the one to move work from.
  • Late work is planned for today. An item past its due date is planned for today and flagged, so the plan never hides it.

Workline’s page on lineset.dev has the waitlist; Workline is not on the Atlassian Marketplace yet.

How fast the team ships, with Changeline

The picture under this page is Changeline’s Trends tab. Changeline counts the releases the team has shipped each week, and the failures among them, so a plan’s pace can be read against the weeks before. Deployment frequency in Jira says how the count works, and The tabs names each tab. 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.

Changeline’s Trends tab, from its tab strip down: deployments each week, stacked into those with no failure and those with one, change lead time each release by its stages, the failures raised each week and the change fail rate in percent of deployments.
Changeline’s Trends tab: the releases each week, their lead time, the failures among them and the change fail rate.

Changeline is coming to the Atlassian Marketplace

Get one email the day it’s live.