<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Khrystyna Dzhus</title>
    <description>The latest articles on DEV Community by Khrystyna Dzhus (@khrystyna_dzhus).</description>
    <link>https://dev.to/khrystyna_dzhus</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4039544%2F4d61e99d-b010-47b1-8a68-ec6506dfc67e.jpg</url>
      <title>DEV Community: Khrystyna Dzhus</title>
      <link>https://dev.to/khrystyna_dzhus</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/khrystyna_dzhus"/>
    <language>en</language>
    <item>
      <title>Jira time in status field: 3 ways to create one and their limits</title>
      <dc:creator>Khrystyna Dzhus</dc:creator>
      <pubDate>Tue, 10 Nov 2026 13:29:49 +0000</pubDate>
      <link>https://dev.to/khrystyna_dzhus/jira-time-in-status-field-3-ways-to-create-one-and-their-limits-30hl</link>
      <guid>https://dev.to/khrystyna_dzhus/jira-time-in-status-field-3-ways-to-create-one-and-their-limits-30hl</guid>
      <description>&lt;p&gt;Say your lead asks a simple question in retro: which tickets sat in code review the longest last sprint? Jira has the answer — every status change is in the issue history. It just doesn't give you a field for it. You can't sort by it, filter on it, or put it on a board card.&lt;/p&gt;

&lt;p&gt;I went through the top Google results for this, and nearly all of them end the same way: install an app. I work at a company that makes one, so I won't pretend apps are useless. But they aren't the only option, and depending on what you need, they may not be the best one.&lt;/p&gt;

&lt;p&gt;So here are three ways to build a time in status field — Jira Automation, a small Python script against the REST API, and &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Time-in-status-field_10112026"&gt;Time in Status app by SaaSJet&lt;/a&gt;. They don't always give the same number, and I'll show you where and why.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is a Jira time in status field?
&lt;/h2&gt;

&lt;p&gt;A &lt;strong&gt;time in status field&lt;/strong&gt; is a custom field that shows how long a work item has spent in a status or a status group, calculated from its status history. You can track a custom field with Jira Automation, calculate and write it through the REST API, or use a Marketplace app that provides the calculation.&lt;/p&gt;

&lt;p&gt;The field becomes useful when everyone understands its definition. For example, “Review time” could mean the latest visit to Review, all visits added together, or only the portions of those visits that overlap working hours. Choose one before you build.&lt;/p&gt;

&lt;p&gt;It isn't time tracking either. A ticket can have two hours of logged work and three days in review — nobody logs waiting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does Jira have a native time in status field?
&lt;/h2&gt;

&lt;p&gt;No. Jira has no built-in time in status custom field. It has two partial ways to see status duration, and it's worth knowing exactly where each stops before you build anything.&lt;/p&gt;

&lt;h3&gt;
  
  
  Days in column
&lt;/h3&gt;

&lt;p&gt;Company-managed boards can show Days in column: a row of dots on each card, one per day. It's useful as a glance, but check three things before you treat it as your metric:&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;It measures a board column, not a status.&lt;/strong&gt; If your Review column maps both In Review and Waiting for Approval, the dots count both.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;It accumulates.&lt;/strong&gt; When a work item returns to a column it was in before, &lt;a href="https://support.atlassian.com/jira/kb/days-in-column-setting-is-missing-from-boards/" rel="noopener noreferrer"&gt;Atlassian's docs&lt;/a&gt; say the indicator shows the cumulative days for that column — not the time since the latest entry. &lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;It isn't a field.&lt;/strong&gt; You can't query it in JQL, sort by it, or export it. Atlassian also recommends leaving it off on very large instances for performance reasons.&lt;/p&gt;

&lt;h3&gt;
  
  
  Native JQL
&lt;/h3&gt;

&lt;p&gt;JQL can tell you whether a work item was in a status, never for how long. The closest you get is "currently in this status for longer than X":&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;project = DEMO
AND status = "In Review"
AND created &amp;lt;= "-2d"
AND NOT (status CHANGED AFTER "-2d")
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This reads: the work item is in review now, it hasn't entered review in the last two days, and it's old enough that "created directly in review" doesn't sneak through.&lt;/p&gt;

&lt;p&gt;The query you'll find more often — status CHANGED TO "In Review" BEFORE -2d — is subtly wrong. It matches any work item that entered review more than two days ago at any point, including one that bounced back into review an hour ago.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What native JQL can't do at all:&lt;/strong&gt; sum repeat visits, compare durations between work items, exclude weekends, or sort by time in status. If you need any of those, you need a field.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define your metric and choose an approach
&lt;/h2&gt;

&lt;p&gt;Most "wrong" time in status values aren't bugs — they're two people using different definitions. Answer five questions before you build:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Which statuses? One status, or a group such as In Review + Waiting for Approval counted as "review time".&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Repeat visits: sum every visit, or count only the latest one?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The open stay: include the visit that hasn't ended yet? If yes, the value is only as fresh as its last recalculation.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Calendar: 24/7, or working hours only?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Unit and precision: hours with two decimals, or whole days?&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  How the three approaches compare
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Jira Automation (basic rules)&lt;/th&gt;
&lt;th&gt;REST API script&lt;/th&gt;
&lt;th&gt;Time in Status by SaaSJet&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Historical backfill&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No — counts only transitions after the rules are on&lt;/td&gt;
&lt;td&gt;Yes — reads the full changelog&lt;/td&gt;
&lt;td&gt;Recalculates every item in scope on each run&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Current open stay&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No, without an extra scheduled rule&lt;/td&gt;
&lt;td&gt;Yes, as of the last run&lt;/td&gt;
&lt;td&gt;Yes, as of the last run (&lt;em&gt;Current status&lt;/em&gt; mode)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Repeat visits&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes, if the rule adds to a running total&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Check with the test below&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Status groups&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;One rule pair per status&lt;/td&gt;
&lt;td&gt;Yes — a set of status IDs&lt;/td&gt;
&lt;td&gt;Yes — &lt;em&gt;Selected statuses&lt;/em&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Working hours&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Whole business days only, no hours or holidays&lt;/td&gt;
&lt;td&gt;You write it&lt;/td&gt;
&lt;td&gt;Yes — linked work schedule&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Queryable in JQL&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Yes — Number field&lt;/td&gt;
&lt;td&gt;Yes — Number field&lt;/td&gt;
&lt;td&gt;Yes — durations like &lt;code&gt;2h&lt;/code&gt;, &lt;code&gt;1d&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;When the value updates&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;When the issue leaves the status&lt;/td&gt;
&lt;td&gt;On each scheduled run&lt;/td&gt;
&lt;td&gt;Hourly, daily, or weekly, or &lt;em&gt;Update now&lt;/em&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Side effects of updates&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Each edit adds to issue history&lt;/td&gt;
&lt;td&gt;Each write adds to issue history&lt;/td&gt;
&lt;td&gt;Not documented — check the issue history&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Maintenance&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Rules per status&lt;/td&gt;
&lt;td&gt;Script, scheduler, API token&lt;/td&gt;
&lt;td&gt;Admin setup; the vendor maintains the calculation&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Which one to pick
&lt;/h3&gt;

&lt;p&gt;• &lt;strong&gt;Jira Automation&lt;/strong&gt; if you track one or two statuses, only care about work items from now on, and nobody wants to own code.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;REST API script&lt;/strong&gt; if you need history from day one, status groups, or full control over the definition — and someone will own the script.&lt;/p&gt;

&lt;p&gt;• A &lt;strong&gt;Marketplace app&lt;/strong&gt; if you need many fields, working calendars, or admins who shouldn't maintain scripts. It's also the honest answer once your script starts growing features.&lt;/p&gt;

&lt;h2&gt;
  
  
  Create a time in status field with Jira Automation
&lt;/h2&gt;

&lt;p&gt;The Automation version is two rules: stamp the time when an issue enters the status, and add the elapsed time to a running total when it leaves. &lt;/p&gt;

&lt;p&gt;It's the approach in &lt;a href="https://support.atlassian.com/jira/kb/get-the-amount-of-time-a-jira-issue-was-in-a-status-using-automation/" rel="noopener noreferrer"&gt;Atlassian's own recipe&lt;/a&gt;, with two fixes for precision and repeat visits.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Create two custom fields&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;• Review entered at — Date Time Picker.&lt;/p&gt;

&lt;p&gt;• Time in Review (h) — Number.&lt;/p&gt;

&lt;p&gt;Add both to the contexts for your project and work types. Note their IDs; below they're &lt;code&gt;customfield_10050&lt;/code&gt; and &lt;code&gt;customfield_10051&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Rule A: stamp the entry&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;• Trigger: Work item transitioned → To status: In Review&lt;/p&gt;

&lt;p&gt;• Action: Edit work item fields → Review entered at = &lt;code&gt;{{now}}&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Rule B: add the stay on exit&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;• Trigger: Work item transitioned → From status: In Review&lt;/p&gt;

&lt;p&gt;• Condition: Review entered at is not empty&lt;/p&gt;

&lt;p&gt;• Action: Edit work item fields → Time in Review (h) =&lt;br&gt;
&lt;code&gt;{{#=}}{{issue.customfield_10051|0}} + {{issue.customfield_10050.diff(now).minutes}} / 60{{/}}&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;• Action: Edit work item fields → clear Review entered at&lt;/p&gt;

&lt;p&gt;Two details in that expression matter:&lt;/p&gt;

&lt;p&gt;• &lt;code&gt;|0&lt;/code&gt; makes the first visit work: the total is empty until then, and empty plus a number isn't a number.&lt;/p&gt;

&lt;p&gt;• &lt;code&gt;.minutes / 60&lt;/code&gt; instead of &lt;code&gt;.hours&lt;/code&gt;: a date diff returns whole units, so .hours would turn 1 h 59 min into 1. With minutes, each visit loses less than a minute.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where the Automation field breaks&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;No history.&lt;/strong&gt; Work items that left review before you enabled Rule A stay empty. Work items sitting in review at that moment have no entry stamp, so Rule B skips them and their current visit is lost. Use the REST API script once for backfill if you need it.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;No open stay.&lt;/strong&gt; The total only grows when a work item leaves review. A work item stuck there for five days shows the total of its earlier visits — possibly zero. For "stuck" alerts, use the JQL from the previous section, or add a scheduled rule that writes a separate "including current visit" field. That rule runs against your automation usage limits.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;Created straight into the status.&lt;/strong&gt; No transition means no stamp. Add a third rule on Work item created with the condition Status = In Review.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;Working hours.&lt;/strong&gt; &lt;code&gt;.businessDays&lt;/code&gt; exists, but it counts whole weekdays. No hour schedules, no holidays.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;Every update is an issue change.&lt;/strong&gt; Each edit adds to the issue history and moves Updated. Turn off notifications in the Edit action's options. Other rules won't fire on these edits unless they have Allow rule trigger enabled.&lt;/p&gt;
&lt;h2&gt;
  
  
  Calculate and write the field with the REST API
&lt;/h2&gt;

&lt;p&gt;The script reads each issue's full status history, sums every visit to the target statuses, adds the open visit up to the moment of calculation, and writes the result into a Number field. Unlike the Automation rules, it works on history from day one.&lt;/p&gt;
&lt;h3&gt;
  
  
  Before you run it
&lt;/h3&gt;

&lt;p&gt;• A Number field associated with the project and work types you'll update. On Jira Cloud the field no longer needs to be on the edit screen: &lt;a href="https://community.developer.atlassian.com/t/deprecation-of-override-screen-security/97153" rel="noopener noreferrer"&gt;since October 2025 the issue edit API doesn't require it&lt;/a&gt;, but the field must still be associated with that project and work type. On Data Center, check your version's rules.&lt;/p&gt;

&lt;p&gt;• An API token for an account with Edit work items permission. Suppressing notifications (notifyUsers=false) also needs project or Jira admin permission.&lt;/p&gt;

&lt;p&gt;• Status IDs, not names. Get them from GET /rest/api/3/status. IDs survive renames and translated status names; the names stored in the changelog don't.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The script&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;import os
import time
from datetime import datetime, timezone

import requests

BASE_URL = os.environ["JIRA_BASE_URL"]         # https://your-site.atlassian.net
FIELD_ID = "customfield_10051"                 # Number field: Time in Review (h)
TARGET_STATUS_IDS = {"10003"}                  # one status, or a group of IDs
JQL = os.environ.get("JQL", 'project = ABC AND status WAS "In Review"')

session = requests.Session()
session.auth = (os.environ["JIRA_EMAIL"], os.environ["JIRA_API_TOKEN"])
session.headers["Accept"] = "application/json"


def call(method, path, **kwargs):
    """One Jira call, retried when rate-limited."""
    while True:
        r = session.request(method, BASE_URL + path, **kwargs)
        if r.status_code == 429:
            time.sleep(int(r.headers.get("Retry-After", "10")))
            continue
        r.raise_for_status()
        return r.json() if r.content else None


def parse(ts):
    # Jira timestamps look like 2026-11-03T10:15:22.123+0200
    return datetime.strptime(ts, "%Y-%m-%dT%H:%M:%S.%f%z")


def search(jql):
    """Yield every issue matching the JQL (enhanced search, token paging)."""
    body = {"jql": jql, "fields": ["created", "status", FIELD_ID], "maxResults": 100}
    while True:
        page = call("POST", "/rest/api/3/search/jql", json=body)
        yield from page["issues"]
        if not page.get("nextPageToken"):
            return
        body["nextPageToken"] = page["nextPageToken"]


def status_changes(key):
    """All status transitions as (time, from_id, to_id), oldest first."""
    changes, start = [], 0
    while True:
        page = call("GET", f"/rest/api/3/issue/{key}/changelog",
                    params={"startAt": start, "maxResults": 100})
        for history in page["values"]:
            for item in history["items"]:
                if item.get("fieldId") == "status":
                    changes.append((parse(history["created"]), item["from"], item["to"]))
        start += len(page["values"])
        if page.get("isLast", True) or not page["values"]:
            return sorted(changes)


def hours_in_status(issue, now):
    changes = status_changes(issue["key"])
    entered = parse(issue["fields"]["created"])
    # The status an issue was created in is the "from" of its first transition.
    current = changes[0][1] if changes else issue["fields"]["status"]["id"]
    seconds = 0.0
    for when, _from, to in changes:
        if current in TARGET_STATUS_IDS:
            seconds += (when - entered).total_seconds()
        current, entered = to, when
    if current in TARGET_STATUS_IDS:       # still there: count the open stay
        seconds += (now - entered).total_seconds()
    return round(seconds / 3600, 2)


def main():
    now = datetime.now(timezone.utc)
    for issue in search(JQL):
        value = hours_in_status(issue, now)
        if issue["fields"].get(FIELD_ID) == value:
            continue                         # unchanged: no history noise
        call("PUT", f"/rest/api/3/issue/{issue['key']}",
             params={"notifyUsers": "false"},
             json={"fields": {FIELD_ID: value}})
        print(f"{issue['key']}: {value} h")


if __name__ == "__main__":
    main()
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Run it twice: backfill, then incremental&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Run it once with the default JQL to backfill every issue that was ever in review. Then schedule it — hourly cron or a GitHub Actions schedule — with a narrower query so each run touches only issues whose value can change:&lt;br&gt;
&lt;code&gt;project = ABC AND (status = "In Review" OR status CHANGED FROM "In Review" AFTER -2h)&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;The two-hour window overlaps an hourly schedule, so a late run doesn't miss an exit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where the script breaks&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;• The value is as fresh as the last run. For an issue still in review, the field shows the time up to that run, not up to now.&lt;/p&gt;

&lt;p&gt;• Every write is an issue change. A write through PUT /rest/api/3/issue/{key} moves Updated, adds a history entry, and can trigger Automation rules listening for updates. That's why the script skips unchanged values. Run it as a dedicated integration account and exclude that account in rules that should react only to people. Filters such as updated &amp;gt;= -1d will now also return machine updates.&lt;/p&gt;

&lt;p&gt;• One changelog call per issue. Fine for hundreds of issues, slow for a full backfill of a large instance. The incremental JQL keeps scheduled runs small.&lt;/p&gt;

&lt;p&gt;• 24/7 only. Working hours mean intersecting each interval with a calendar of hours, time zones, and holidays — doable, but it's the point where a script starts turning into a product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Add a time in status field with a Marketplace app
&lt;/h2&gt;

&lt;p&gt;An app gives you the field with the calculation, refresh, and usually working calendars already built. &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Time-in-status-field_10112026"&gt;Time in Status by SaaSJet&lt;/a&gt; is one of the apps that does this.&lt;/p&gt;

&lt;p&gt;Here's what the setup looks like in Time in Status by SaaSJet. A Jira admin creates the field under &lt;em&gt;Jira settings → Apps → Manage apps → Time in Status → Custom fields → Create new field&lt;/em&gt;. The wizard has three steps, and the second one is where the metric decisions from earlier get made.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 1: Name the field
&lt;/h3&gt;

&lt;p&gt;For the test in this article: TIS [Review]. The name must be unique among your custom fields, because it's how you reference the field in JQL.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2: Decide what it measures
&lt;/h3&gt;

&lt;p&gt;• &lt;strong&gt;Where it applies:&lt;/strong&gt; a field scheme plus the work types it covers. That's the native Jira mechanism, so the field works across every project the scheme covers, not just one board.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;Statuses:&lt;/strong&gt; Current status measures how long an item has been wherever it is right now — useful for spotting stuck work. Selected statuses sums the statuses you pick into one metric. For the test: In Review. Add Waiting for Approval and it becomes a review-time group; the same option builds Cycle Time or Lead Time.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;Work schedule:&lt;/strong&gt; 24/7 for raw elapsed time, or a business calendar that skips nights, weekends, and holidays. This is the part that's painful to build in the other two approaches.&lt;/p&gt;

&lt;p&gt;• &lt;strong&gt;Update frequency:&lt;/strong&gt; hourly, daily, or weekly, plus an Update now button.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftypgib0koq71cg2uh9x0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftypgib0koq71cg2uh9x0.png" alt="create custom field" width="800" height="719"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3: Choose screens
&lt;/h3&gt;

&lt;p&gt;Pick the screens where the field should appear. Team-managed projects add it from their own project settings. To show it on cards: Board settings → Card layout → add the field.&lt;/p&gt;

&lt;p&gt;Creating the field doesn't calculate anything yet. Values appear after the first scheduled run or after Update now.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What you see&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;On board cards and in the issue view, the value is shown as days and hours.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcy6zuq79xae2dg8xilyf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcy6zuq79xae2dg8xilyf.png" alt="time in status custom field" width="800" height="349"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Under the hood it's stored in seconds. JQL compares the exact value, not the rounded label, so an item showing 1d can still match &amp;gt; 1d. Through the REST API, fields returns the raw seconds and renderedFields returns the formatted value.&lt;/p&gt;

&lt;p&gt;In JQL, durations are written in days and hours:&lt;br&gt;
&lt;code&gt;"TIS [Review]" &amp;gt; 2h&lt;br&gt;
status = "In Progress" AND "TIS [Review]" &amp;gt;= 1d&lt;br&gt;
ORDER BY "TIS [Review]" DESC&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Where the app field breaks&lt;/p&gt;

&lt;p&gt;• Workflow changes need attention. If a grouped status is removed from the workflow, its time stops counting and the app flags the field.&lt;br&gt;
• Setup is admin-only. Creating and managing fields requires Administer Jira.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Don't want to maintain rules or a script? Try &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Time-in-status-field_10112026"&gt;Time in Status by SaaSJet&lt;/a&gt; with a free trial from the Atlassian Marketplace. Create a field for your statuses, link a work schedule, and run the same test from this article on your own work items. &lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>jira</category>
      <category>automation</category>
      <category>python</category>
      <category>productivity</category>
    </item>
    <item>
      <title>[Boost]</title>
      <dc:creator>Khrystyna Dzhus</dc:creator>
      <pubDate>Thu, 05 Nov 2026 13:24:07 +0000</pubDate>
      <link>https://dev.to/khrystyna_dzhus/-1gg9</link>
      <guid>https://dev.to/khrystyna_dzhus/-1gg9</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/khrystyna_dzhus/i-turned-a-jira-time-in-status-report-into-4-charts-one-of-them-lied-to-me-at-first-2fhe" class="crayons-story__hidden-navigation-link"&gt;I Turned a Jira Time in Status Report Into 4 Charts. One of Them Lied to Me at First&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/khrystyna_dzhus" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4039544%2F4d61e99d-b010-47b1-8a68-ec6506dfc67e.jpg" alt="khrystyna_dzhus profile" class="crayons-avatar__image"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/khrystyna_dzhus" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Khrystyna Dzhus
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Khrystyna Dzhus
                
                
              
              &lt;div id="story-author-preview-content-4982218" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/khrystyna_dzhus" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4039544%2F4d61e99d-b010-47b1-8a68-ec6506dfc67e.jpg" class="crayons-avatar__image" alt=""&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Khrystyna Dzhus&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/khrystyna_dzhus/i-turned-a-jira-time-in-status-report-into-4-charts-one-of-them-lied-to-me-at-first-2fhe" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Nov 5&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/khrystyna_dzhus/i-turned-a-jira-time-in-status-report-into-4-charts-one-of-them-lied-to-me-at-first-2fhe" id="article-link-4982218"&gt;
          I Turned a Jira Time in Status Report Into 4 Charts. One of Them Lied to Me at First
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/jira"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;jira&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/agile"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;agile&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/productivity"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;productivity&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/devops"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;devops&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/khrystyna_dzhus/i-turned-a-jira-time-in-status-report-into-4-charts-one-of-them-lied-to-me-at-first-2fhe" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/fire-f60e7a582391810302117f987b22a8ef04a2fe0df7e3258a5f49332df1cec71e.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;6&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/khrystyna_dzhus/i-turned-a-jira-time-in-status-report-into-4-charts-one-of-them-lied-to-me-at-first-2fhe#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              1&lt;span class="hidden s:inline"&gt;&amp;nbsp;comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            7 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;


</description>
      <category>analytics</category>
      <category>management</category>
      <category>productivity</category>
    </item>
    <item>
      <title>I Turned a Jira Time in Status Report Into 4 Charts. One of Them Lied to Me at First</title>
      <dc:creator>Khrystyna Dzhus</dc:creator>
      <pubDate>Thu, 05 Nov 2026 13:19:18 +0000</pubDate>
      <link>https://dev.to/khrystyna_dzhus/i-turned-a-jira-time-in-status-report-into-4-charts-one-of-them-lied-to-me-at-first-2fhe</link>
      <guid>https://dev.to/khrystyna_dzhus/i-turned-a-jira-time-in-status-report-into-4-charts-one-of-them-lied-to-me-at-first-2fhe</guid>
      <description>&lt;p&gt;A time in status table tells you everything and shows you nothing. I took one time in status report, built four charts from it, and used each one to answer a single workflow question: where time accumulates, whether long waits are the rule or the exception, which work items to check first, and whether estimates match reality. Along the way, one chart gave me a completely wrong picture because of a single checkbox. Details below.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work at SaaSJet, the team behind the &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Time-in-status-charts_05112026"&gt;Time in Status app by SaaSJet&lt;/a&gt; used in this post.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem with a perfectly good table
&lt;/h2&gt;

&lt;p&gt;Jira records every status change in each work item's history. &lt;strong&gt;Time in status&lt;/strong&gt; is simply the time between those changes: how long an item sat in In Progress, On review, Testing, and so on.&lt;/p&gt;

&lt;p&gt;A time in status report turns that history into a table. Which is great until the table has 100+ rows and a dozen status columns. At that point, the work items that need attention look exactly like the ones that don't. You end up scanning cells, and nobody does that during a stand-up.&lt;/p&gt;

&lt;p&gt;So instead of reading the table, I started asking it questions, one chart per question.&lt;/p&gt;

&lt;h2&gt;
  
  
  Question 1: Where does time accumulate across projects?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Setup:&lt;/strong&gt; Stacked column · Categories: Project · Aggregate: Average · Series: In Progress, On review, Testing&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fha5om0sc43jqp2xi4j32.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fha5om0sc43jqp2xi4j32.png" alt="time in status stacked projects" width="800" height="424"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I compared two projects. Using &lt;strong&gt;Average&lt;/strong&gt; instead of Sum matters here: the projects have different numbers of work items, and a sum would just reward the smaller one.&lt;/p&gt;

&lt;p&gt;The result was more interesting than I expected. Work items in the Design project took nearly twice as long on average as those in Core App, and most of that difference was in review. In Design, items spent about 2.5 days On review, which is &lt;em&gt;longer&lt;/em&gt; than the 2.2 days they spent In Progress. Review took more time than the work itself.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Before you trust a chart like this:&lt;/strong&gt; compare only the statuses both projects actually use. Design has no Testing status at all, so part of the height difference comes from a different workflow, not slower work. This chart tells you where to look closer. It is not a team ranking.&lt;/p&gt;

&lt;h2&gt;
  
  
  Question 2: Is "long review" a pattern or a few bad cases?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Setup:&lt;/strong&gt; Histogram · Series: On review · Aggregate: off&lt;/p&gt;

&lt;p&gt;An average of 2.5 days can mean two very different things: most items wait about 2.5 days, or most pass quickly while a few sit there for weeks. The table and the average look identical in both cases. A histogram doesn't.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F833pqeyfw8zqsky8qu66.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F833pqeyfw8zqsky8qu66.png" alt="Histogram of time spent in On review" width="799" height="428"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For the Design project, I narrowed the report to items that actually went through review:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="n"&gt;project&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;Design&lt;/span&gt; &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="n"&gt;WAS&lt;/span&gt; &lt;span class="nv"&gt;"On review"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Without that filter, items that never entered review show up as a tall bar at zero and distort everything.&lt;/p&gt;

&lt;p&gt;What the histogram showed: &lt;strong&gt;49 of 63&lt;/strong&gt; work items left review in under six days. Eleven took six to seventeen days. Three stayed in review for two and a half to almost six weeks.&lt;/p&gt;

&lt;p&gt;So the average described nobody. Not the typical item, and not the problem work items. Those three long cases were dragging it up.&lt;/p&gt;

&lt;p&gt;In latency terms, this is the p50/p85 conversation. Roughly 78% of work items left review within six days. "Most reviews finish within a week" is a far more useful expectation for the team than "the average review takes 2.5 days".&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What to do with this:&lt;/strong&gt; start with the far right. A month in review almost never means a month of reviewing. It usually means blocked, waiting for a decision, or forgotten. Then look at the middle group: a dozen items regularly taking one to two weeks is a process conversation, not a list of exceptions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Question 3: Which work items should I open first?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Setup:&lt;/strong&gt; Grouped bar · Categories: Work item key · Series: In Progress, Ready for Testing, Testing&lt;/p&gt;

&lt;p&gt;Once you know there are outliers, you need their keys. Here's the trick that made this chart readable: &lt;strong&gt;sort the table by the status you care about, select the top 8–10 rows, and build the chart from that selection.&lt;/strong&gt; With 30+ items, the bars turn into threads and you can't compare anything.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxrmpn043s9vq88zvax2q.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxrmpn043s9vq88zvax2q.png" alt="Grouped bar chart of time in status per work item" width="800" height="427"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Two items spent more than 12 hours in In Progress, about four times longer than anything else in the selection. Their Ready for Testing and Testing times were short, so the delay happened during development, not in the handoff to QA.&lt;/p&gt;

&lt;p&gt;A long bar tells you &lt;em&gt;where&lt;/em&gt; to look, not &lt;em&gt;why&lt;/em&gt;. Check whether the item was blocked, reassigned, or just bigger than it looked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Question 4: Do items with the same estimate take the same time?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Setup:&lt;/strong&gt; Scatter · X: Story Points · Y: Total · Labels: Work item key · Aggregate: off&lt;/p&gt;

&lt;p&gt;This is the chart you simply can't get from a table. Each point is one work item, placed by its estimate and the time it actually spent in the workflow.&lt;/p&gt;

&lt;p&gt;I used one project only (estimation scales differ between teams) and filtered to finished, estimated items:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="n"&gt;project&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nv"&gt;"Core App"&lt;/span&gt; &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="n"&gt;statusCategory&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;Done&lt;/span&gt; &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="nv"&gt;"Story Points"&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb795a2k1gci7skvlm4sk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb795a2k1gci7skvlm4sk.png" alt="Scatter plot of story points vs total time in status" width="799" height="424"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The overall trend made sense: bigger estimates generally took longer. But within the same estimate, the spread was huge. Work items estimated at 3 points took anywhere from a few hours to about 12 days. One 22-point item finished faster than the slowest 3-pointer. A 17-point item spent almost four weeks in the workflow.&lt;/p&gt;

&lt;p&gt;A wide spread doesn't prove the estimates were bad. It shows where the workflow added time that no estimate could predict. The next step is to take two items with the same estimate and very different totals and compare their status histories side by side.&lt;/p&gt;

&lt;h2&gt;
  
  
  The chart that lied to me (and the gotchas I'd check every time)
&lt;/h2&gt;

&lt;p&gt;My first version of the scatter plot was useless. Dozens of points lined up at exactly &lt;strong&gt;~62 days&lt;/strong&gt;, regardless of the estimate. A 1-point item and a 22-point item looked identical.&lt;/p&gt;

&lt;p&gt;62 days turned out to be the length of my reporting period. The total was the sum of all 13 statuses in the report, &lt;strong&gt;including Done&lt;/strong&gt;. An item closed on day two kept "accumulating" time in Done until the end of the period. The chart was showing when items were created and closed, not how long the work took.&lt;/p&gt;

&lt;p&gt;The fix was to keep only statuses where work is actually happening (In Progress, On Review, Ready for Testing, Testing, Blocked) and remove Done, To Do, Backlog, and anything that means "not started" or "already finished". The y-axis dropped from 69 days to 28, and the real picture appeared.&lt;/p&gt;

&lt;p&gt;This isn't a quirk of one tool. Open-source flow tools like &lt;a href="https://github.com/DeloitteDigitalUK/jira-agile-metrics" rel="noopener noreferrer"&gt;jira-agile-metrics&lt;/a&gt; make you define where work starts and ends in their config for exactly this reason: cycle time only means something once backlog and done time are out of it.&lt;/p&gt;

&lt;p&gt;My checklist now, before reading any time in status chart:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;What's inside Total?&lt;/strong&gt; If it includes Done or backlog statuses, you're measuring age, not work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Are unfinished work items in the data?&lt;/strong&gt; Open items keep accumulating time until the end of the period. Filter with &lt;code&gt;statusCategory = Done&lt;/code&gt; when you compare durations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Are there empty values?&lt;/strong&gt; Items without story points or without a given status can pile up at zero.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Duplicate or legacy statuses?&lt;/strong&gt; Workflows change, but history doesn't. My report had both "Todo" and "To Do". Exclude one and forget the other, and your numbers quietly drift.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How does your team mark blocked work?&lt;/strong&gt; If it uses Jira's Flag instead of a Blocked status, time in status won't show blocked time at all. It will look like regular In Progress time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sum or Average?&lt;/strong&gt; Use Average when groups have different sizes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Same workflow?&lt;/strong&gt; Comparing projects with different statuses compares workflows, not teams.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How the charts are built
&lt;/h2&gt;

&lt;p&gt;All four charts came from table reports in &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Time-in-status-charts_05112026"&gt;Time in Status app&lt;/a&gt;. You either select a range of cells and choose &lt;strong&gt;Chart range&lt;/strong&gt;, or open &lt;strong&gt;Charts → Create chart&lt;/strong&gt; in the sidebar and pick the categories, series, and aggregation. The builder has 13 chart types, and the charts stay Live, so they update when the report data changes. You can also add them to a Jira dashboard through the app's gadgets. More in the &lt;a href="https://saasjet.com/blog/jira-chart-time-in-status/" rel="noopener noreferrer"&gt;original article&lt;/a&gt; and the &lt;a href="https://saasjet.atlassian.net/wiki/spaces/TIS/pages/5400756233/Integrated+charts" rel="noopener noreferrer"&gt;Integrated charts documentation&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you'd rather script this, &lt;a href="https://github.com/DeloitteDigitalUK/jira-agile-metrics" rel="noopener noreferrer"&gt;jira-agile-metrics&lt;/a&gt; is an open-source CLI that pulls cycle time, histograms, and scatter plots straight from the Jira API. I wanted the charts inside Jira, next to the table I was already using, so I went with the app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Over to you
&lt;/h2&gt;

&lt;p&gt;Which workflow question keeps coming up in your retros without a clear answer? And has a chart ever confidently shown you something that turned out to be a data artifact? I'd love to hear your stories in the comments.&lt;/p&gt;

</description>
      <category>jira</category>
      <category>agile</category>
      <category>productivity</category>
      <category>devops</category>
    </item>
    <item>
      <title>Jira Time in Status: Check What’s Hiding in Your Workflow</title>
      <dc:creator>Khrystyna Dzhus</dc:creator>
      <pubDate>Tue, 13 Oct 2026 20:58:14 +0000</pubDate>
      <link>https://dev.to/khrystyna_dzhus/jira-time-in-status-check-whats-hiding-in-your-workflow-2pfo</link>
      <guid>https://dev.to/khrystyna_dzhus/jira-time-in-status-check-whats-hiding-in-your-workflow-2pfo</guid>
      <description>&lt;p&gt;Every team has been there. Tasks are moving, people are busy, and yet delivery is slow. A feature that was planned to take a week takes three. Nobody understands where the time actually goes.&lt;/p&gt;

&lt;p&gt;The total duration can tell you that the work is slow, but it doesn't tell you where it slows down.&lt;/p&gt;

&lt;p&gt;The metric that answers "where" is time in status. In this post, I'll cover what it measures, what Jira gives you out of the box, and how to calculate it with the Time in Status app for Jira, so you can see where work slows down and act on it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What time in status actually measures
&lt;/h2&gt;

&lt;p&gt;Time in status is a metrics that tracks how long work items spend in workflow statuses. Instead of a total number, it gives a breakdown. For example, the workflow of a work item may look like that:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Status&lt;/th&gt;
&lt;th&gt;Time spent&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;In Progress&lt;/td&gt;
&lt;td&gt;2 days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Waiting for Code Review&lt;/td&gt;
&lt;td&gt;4 days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Code Review&lt;/td&gt;
&lt;td&gt;1 day&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Waiting for QA Review&lt;/td&gt;
&lt;td&gt;2 days&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;QA Review&lt;/td&gt;
&lt;td&gt;1 day&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Based on this, we can see that the work item spent 6 of 10 days in "waiting" status. It is also important to clarify whether the 2 days spent in "In Progress" status represent active work or include waiting time.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to track time in status in Jira?
&lt;/h2&gt;

&lt;p&gt;There are several options that allow to get time in status report in Jira.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Days in column&lt;/strong&gt; displays a visual age indicator on cards on supported boards when enabled. It measures column time; a column can contain multiple statuses, so it is not necessarily the duration of one status.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Control Chart&lt;/strong&gt; uses time spent in selected statuses mapped to board columns to help you inspect cycle time, variation, and outliers. You can narrow the selection to investigate part of the workflow.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Native Jira REST API.&lt;/strong&gt; Jira doesn’t store time in status as a single field, so you request the issue history (changelog) and calculate the durations between timestamps yourself.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;ul&gt;
&lt;li&gt;Endpoints:&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One issue: &lt;/p&gt;

&lt;p&gt;&lt;code&gt;GET /rest/api/3/issue/{issueIdOrKey}/changelog&lt;br&gt;
&lt;/code&gt;&lt;br&gt;
Fetch every page to retrieve the complete transition history.&lt;/p&gt;

&lt;p&gt;Many issues: &lt;code&gt;GET or POST /rest/api/3/search/jql&lt;/code&gt; with expand=changelog. It pages with &lt;em&gt;nextPageToken&lt;/em&gt; instead of &lt;em&gt;startAt&lt;/em&gt;. The older &lt;code&gt;/rest/api/3/search&lt;/code&gt; endpoint has been removed from Jira Cloud (CHANGE-2046).&lt;/p&gt;

&lt;p&gt;How it works:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Fetch every page of history until there are no more.&lt;/li&gt;
&lt;li&gt;Keep only items where field equals "status".&lt;/li&gt;
&lt;li&gt;Sort the transitions by their created timestamp.&lt;/li&gt;
&lt;li&gt;For each transition, add the time since the previous one to the status the issue was leaving. Sum per status: an issue that goes In Progress → Review → In Progress gets both In Progress visits counted. Using only the first and last timestamps makes waiting time look smaller than it is.&lt;/li&gt;
&lt;li&gt;For the current status, count from the last transition to now, or stop the clock if the issue is resolved.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;4. Marketplace apps like Time in Status by SaaSJet&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One of the limitations of native approach is that it counts calendar time. This can make a work item’s time in status look longer than it is within your team’s working hours.&lt;/p&gt;

&lt;p&gt;Marketplace apps such as &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Jira-time-in-status_13102026"&gt;Time in Status by SaaSJet&lt;/a&gt; allow to create time in status reports from the same Jira history, but let you set working calendars with business hours, time zones and holidays. This gives you status durations that reflect your team’s actual work schedule.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe6vu0xvs3kj9mzq6wk6p.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe6vu0xvs3kj9mzq6wk6p.png" alt="time in status report" width="799" height="225"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What to look for in the numbers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Waiting stages that dominate the journey&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If “Waiting for Review” takes longer than “In Progress,” ask what controls entry into review. Is there a reviewer assigned? Does anyone pick work up from that queue? Are reviews happening in large batches?&lt;/p&gt;

&lt;p&gt;Start with a few comparable work items. One long wait is a case to investigate; repeated long waits are a stronger reason to examine the process.&lt;/p&gt;

&lt;p&gt;This leads to flow efficiency:&lt;br&gt;
&lt;code&gt;Flow efficiency = active time / (active time + waiting time) × 100%&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;For the illustrative table above, classifying In Progress, Code Review, and QA as active gives 4 / 10 × 100 = 40%.&lt;/p&gt;

&lt;p&gt;Treat that as a status-based estimate. It only reflects actual active and waiting time as well as your workflow captures those distinctions.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq6r7pc1blg1zwn6iqzlr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq6r7pc1blg1zwn6iqzlr.png" alt=" " width="800" height="429"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Repeated visits that totals hide&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Consider this sequence:&lt;br&gt;
In Progress → In Review → In Progress → In Review → Done&lt;/p&gt;

&lt;p&gt;Summing per status combines both visits. That gives you the total duration, but hides the back-and-forth.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F24z99ekcxoqdrwk7nm60.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F24z99ekcxoqdrwk7nm60.png" alt=" " width="799" height="202"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;To investigate possible rework, retain the transition sequence and count entries into each status alongside the durations. Did review uncover a defect? Did requirements change? Was the work item moved back for an administrative reason?&lt;/p&gt;

&lt;p&gt;Repeated entries are a signal to investigate, not proof of poor quality. A long single visit and several short visits can produce the same total while telling very different stories.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the DIY approach breaks
&lt;/h2&gt;

&lt;p&gt;The subtraction is easy. Making the numbers dependable for a whole team takes more work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Working hours and calendars: business-time calculations need working intervals, holidays, time zones, and daylight-saving rules. Dividing calendar hours by eight does not remove non-working time.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Pagination: both endpoints page their results, and every page needs to be fetched successfully.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Hundreds of work items: you need work-item discovery, rate-limit handling, retries, and consistent reporting boundaries. Work items changing during a run can also produce inconsistent snapshots.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Team dashboards: someone must maintain refreshes, filters, access, visualizations, and definitions everyone understands.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ready-made apps such as &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Jira-time-in-status_13102026"&gt;Time in Status by SaaSJet&lt;/a&gt; exist for teams that need calendar-aware reports and shared dashboards.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Full disclosure: I work at SaaSJet.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Which status do your work items get stuck in the longest?&lt;/p&gt;

</description>
      <category>jira</category>
      <category>agile</category>
      <category>productivity</category>
      <category>tooling</category>
    </item>
    <item>
      <title>[Boost]</title>
      <dc:creator>Khrystyna Dzhus</dc:creator>
      <pubDate>Mon, 24 Aug 2026 12:51:08 +0000</pubDate>
      <link>https://dev.to/khrystyna_dzhus/-1o48</link>
      <guid>https://dev.to/khrystyna_dzhus/-1o48</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/khrystyna_dzhus/your-developers-are-coding-faster-so-why-is-delivery-still-slow-2f3a" class="crayons-story__hidden-navigation-link"&gt;Your Developers Are Coding Faster. So Why Is Delivery Still Slow?&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/khrystyna_dzhus" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4039544%2F4d61e99d-b010-47b1-8a68-ec6506dfc67e.jpg" alt="khrystyna_dzhus profile" class="crayons-avatar__image"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/khrystyna_dzhus" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Khrystyna Dzhus
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Khrystyna Dzhus
                
                
              
              &lt;div id="story-author-preview-content-4475615" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/khrystyna_dzhus" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4039544%2F4d61e99d-b010-47b1-8a68-ec6506dfc67e.jpg" class="crayons-avatar__image" alt=""&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Khrystyna Dzhus&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/khrystyna_dzhus/your-developers-are-coding-faster-so-why-is-delivery-still-slow-2f3a" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Aug 24&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/khrystyna_dzhus/your-developers-are-coding-faster-so-why-is-delivery-still-slow-2f3a" id="article-link-4475615"&gt;
          Your Developers Are Coding Faster. So Why Is Delivery Still Slow?
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/ai"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;ai&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/webdev"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;webdev&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/programming"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;programming&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/productivity"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;productivity&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/khrystyna_dzhus/your-developers-are-coding-faster-so-why-is-delivery-still-slow-2f3a" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/raised-hands-74b2099fd66a39f2d7eed9305ee0f4553df0eb7b4f11b01b6b1b499973048fe5.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/multi-unicorn-b44d6f8c23cdd00964192bedc38af3e82463978aa611b4365bd33a0f1f4f3e97.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="18" height="18"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;8&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/khrystyna_dzhus/your-developers-are-coding-faster-so-why-is-delivery-still-slow-2f3a#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              &lt;span class="hidden s:inline"&gt;Add&amp;nbsp;Comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            9 min read
          &lt;/small&gt;
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;

&lt;/div&gt;


</description>
    </item>
    <item>
      <title>Your Developers Are Coding Faster. So Why Is Delivery Still Slow?</title>
      <dc:creator>Khrystyna Dzhus</dc:creator>
      <pubDate>Mon, 24 Aug 2026 12:27:23 +0000</pubDate>
      <link>https://dev.to/khrystyna_dzhus/your-developers-are-coding-faster-so-why-is-delivery-still-slow-2f3a</link>
      <guid>https://dev.to/khrystyna_dzhus/your-developers-are-coding-faster-so-why-is-delivery-still-slow-2f3a</guid>
      <description>&lt;p&gt;More and more developers are using AI assistants to write code. With these tools, teams can move from an idea to implementation much faster than before. Logically, overall delivery should speed up as well — but often not as much as we would expect.&lt;/p&gt;

&lt;p&gt;A team might reduce implementation time by 30% or even 50%, while the time it takes for a feature to actually reach production changes only slightly.&lt;br&gt;
The reason is that other stages of the workflow — waiting for code review, QA, testing, approvals, and release — do not automatically speed up just because coding does.&lt;/p&gt;

&lt;p&gt;That’s why it’s important to ask: if AI has significantly accelerated coding, why isn’t overall delivery time improving at the same pace?&lt;/p&gt;
&lt;h2&gt;
  
  
  Coding time is only one part of delivery time
&lt;/h2&gt;

&lt;p&gt;Let’s imagine a typical workflow in a development team:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;To Do → Development → Code Review → Awaiting QA 
→ Testing → Ready for Release → Done
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;By breaking down the time in the status in more detail, you can see the following picture:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;2 days in Development&lt;/li&gt;
&lt;li&gt;2 days waiting for review&lt;/li&gt;
&lt;li&gt;3 days waiting for QA&lt;/li&gt;
&lt;li&gt;1 day in Testing&lt;/li&gt;
&lt;li&gt;2 days waiting for release&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Development time&lt;/strong&gt;: 2 days. &lt;strong&gt;Total delivery time&lt;/strong&gt;: 10 days.&lt;/p&gt;

&lt;p&gt;With AI becoming part of the development process, it’s entirely possible to cut implementation time in half. In our example, that means cutting it from 2 days to 1.&lt;/p&gt;

&lt;p&gt;That's a 50% improvement in Development.&lt;/p&gt;

&lt;p&gt;But if everything else stays the same, the total delivery time drops from 10 days to 9, &lt;strong&gt;which is only a 10% improvement&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The team really did get faster at writing code — the improvement just happened in one part of a much larger delivery system. &lt;/p&gt;

&lt;h2&gt;
  
  
  Faster coding can expose the next constraint
&lt;/h2&gt;

&lt;p&gt;Think of the workflow as a sequence of stages, each with its own capacity.&lt;br&gt;
When Development becomes faster, more work can reach downstream stages sooner.&lt;/p&gt;

&lt;p&gt;If Code Review, QA, Testing, or Release have enough capacity to absorb that work, delivery improves.&lt;/p&gt;

&lt;p&gt;If they don't, some of the productivity gain turns into queue time.&lt;/p&gt;

&lt;p&gt;The delay hasn't necessarily disappeared. Part of it has moved downstream.&lt;br&gt;
That can show up in several places.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Code Review.&lt;/strong&gt; Developers open PRs faster, but reviewer availability stays the same. Development gets shorter while the review queue gets longer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;QA.&lt;/strong&gt; More work becomes ready for QA, but QA capacity, test environments, and test data haven't changed. Items begin to accumulate in Awaiting QA.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Testing.&lt;/strong&gt; More changes reaching Testing can increase regression scope, environment contention, or coordination work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Release.&lt;/strong&gt; The feature is implemented and tested but still sits in Ready for Release, Approved, or Pending Deployment, waiting for a release window, approval, dependency, or another team.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This doesn't mean faster coding is useless.&lt;/p&gt;

&lt;p&gt;It means the next opportunity for improvement may no longer be in Development.&lt;/p&gt;
&lt;h2&gt;
  
  
  Don't measure the stage you optimized in isolation
&lt;/h2&gt;

&lt;p&gt;Suppose a team starts using AI coding tools and sees this:&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Before&lt;/em&gt;&lt;br&gt;
&lt;code&gt;Development: 4.0 days&lt;br&gt;
&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;After&lt;/em&gt;&lt;br&gt;
&lt;code&gt;Development: 2.0 days&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;A 50% reduction looks impressive.&lt;/p&gt;

&lt;p&gt;And it is.&lt;/p&gt;

&lt;p&gt;But now look at the full path.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Before&lt;/em&gt;&lt;br&gt;
&lt;code&gt;Development        4.0 days&lt;br&gt;
Code Review        1.0 day&lt;br&gt;
Awaiting QA        1.5 days&lt;br&gt;
Testing            1.5 days&lt;br&gt;
Ready for Release  2.0 days&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Total: &lt;strong&gt;10 days&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;After&lt;/em&gt;&lt;br&gt;
&lt;code&gt;Development        2.0 days&lt;br&gt;
Code Review        1.5 days&lt;br&gt;
Awaiting QA        2.0 days&lt;br&gt;
Testing            1.5 days&lt;br&gt;
Ready for Release  2.0 days&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Total: &lt;strong&gt;9 days&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Development improved by 50%.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Overall delivery improved by 10%.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That's still a real improvement. But it tells a very different story from looking at Development alone.&lt;/p&gt;

&lt;p&gt;It also gives the team a much better question to investigate:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;What is limiting the other 90% of the delivery path?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2&gt;
  
  
  Overall cycle time isn't enough either
&lt;/h2&gt;

&lt;p&gt;Looking only at Development can hide downstream delays.&lt;/p&gt;

&lt;p&gt;But looking only at total cycle time has the opposite problem: it tells you that delivery is slow &lt;em&gt;without telling you why&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Suppose your average cycle time is 11.5 days.&lt;/p&gt;

&lt;p&gt;That gives you the end-to-end number.&lt;/p&gt;

&lt;p&gt;But those 11.5 days might consist of very different things:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;Active Development&lt;br&gt;
Code Review&lt;br&gt;
Waiting for QA&lt;br&gt;
Testing&lt;br&gt;
Blocked time&lt;br&gt;
Approval delays&lt;br&gt;
Waiting for deployment&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Each one has a different cause and a different fix.&lt;/p&gt;

&lt;p&gt;So if you want to understand why delivery isn't improving as quickly as coding productivity, you need to break the total down by workflow stage.&lt;/p&gt;
&lt;h2&gt;
  
  
  Break delivery time down by status
&lt;/h2&gt;

&lt;p&gt;Here's an example for 50 recently completed Jira work items:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;Workflow stage&lt;br&gt;
Average time&lt;br&gt;
Development&lt;br&gt;
1.8 days&lt;br&gt;
Code Review&lt;br&gt;
1.2 days&lt;br&gt;
Awaiting QA&lt;br&gt;
3.4 days&lt;br&gt;
Testing&lt;br&gt;
1.5 days&lt;br&gt;
Ready for Release&lt;br&gt;
2.7 days&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Development takes 1.8 days.&lt;/p&gt;

&lt;p&gt;Awaiting QA and Ready for Release together take more than six.&lt;/p&gt;

&lt;p&gt;At this point, reducing Development from 1.8 days to 1 day would certainly help.&lt;/p&gt;

&lt;p&gt;But &lt;strong&gt;it would not transform delivery&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The bigger questions are:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Why does work spend 3.4 days waiting for QA?&lt;br&gt;
and:&lt;/p&gt;

&lt;p&gt;Why does tested work spend another 2.7 days waiting for release?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That's where the difference between developer productivity and delivery performance becomes visible.&lt;/p&gt;
&lt;h2&gt;
  
  
  How to check this in Jira
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.atlassian.com/software/jira" rel="noopener noreferrer"&gt;Jira&lt;/a&gt; already stores the underlying history.&lt;/p&gt;

&lt;p&gt;Every status transition is recorded in the issue changelog with a timestamp.&lt;/p&gt;

&lt;p&gt;The challenge is aggregation. Looking at the history of one issue tells you what happened to that issue. It doesn't tell you whether the same pattern exists across a sprint, release, project, or team.&lt;/p&gt;

&lt;p&gt;There are two basic approaches.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Build the calculation yourself.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;For individual issues, Jira provides:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;GET /rest/api/3/issue/{issueIdOrKey}/changelog
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For multiple issues, you can use:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;POST /rest/api/3/changelog/bulkfetch
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;From there, you can extract status transitions and calculate how long each item stayed in each status.&lt;/p&gt;

&lt;p&gt;The basic calculation isn't especially complicated. The edge cases are.&lt;/p&gt;

&lt;p&gt;You also need to decide how to handle:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;non-working hours&lt;/li&gt;
&lt;li&gt;weekends and holidays&lt;/li&gt;
&lt;li&gt;work items that enter the same status multiple times&lt;/li&gt;
&lt;li&gt;open items that haven't completed yet&lt;/li&gt;
&lt;li&gt;different work schedules&lt;/li&gt;
&lt;li&gt;outliers&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;2. Use a Time in Status report.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Another much simpler way is to use &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=Dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Developers-coding-faster-delivery-still-slows_24082026" rel="noopener noreferrer"&gt;Time in Status app by SaaSJet&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It aggregates Jira status history across multiple work items and shows how much time they spend in different workflow stages without requiring you to calculate the changelog manually.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fek4qsc5xstn1wstfa3a1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fek4qsc5xstn1wstfa3a1.png" alt=" " width="799" height="225"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Whichever approach you use, the analysis itself matters more than the tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with a meaningful comparison
&lt;/h2&gt;

&lt;p&gt;If you're trying to understand whether faster Development is translating into faster delivery, don't just compare one sprint with another randomly.&lt;/p&gt;

&lt;p&gt;Use comparable periods or groups of work.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;several sprints before and after introducing AI tooling&lt;/li&gt;
&lt;li&gt;similar releases&lt;/li&gt;
&lt;li&gt;the same team over two comparable periods&lt;/li&gt;
&lt;li&gt;similar issue types or work categories&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For cycle-time analysis, completed items give you a defined start and endpoint.&lt;/p&gt;

&lt;p&gt;But don't ignore current WIP entirely.&lt;/p&gt;

&lt;p&gt;If ten open tickets have already been sitting in Awaiting QA for two weeks, excluding them can make your completed-item numbers look healthier than the process really is.&lt;/p&gt;

&lt;p&gt;Use completed work for consistent cycle-time comparisons, then inspect long-running open work separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Look at average and median together
&lt;/h2&gt;

&lt;p&gt;Status-duration data is rarely perfectly distributed.&lt;/p&gt;

&lt;p&gt;Imagine most work items spend one or two days waiting for QA, while three items wait for two weeks.&lt;/p&gt;

&lt;p&gt;The average can move dramatically.&lt;/p&gt;

&lt;p&gt;The median may barely move at all.&lt;/p&gt;

&lt;p&gt;So don't rely on one aggregate.&lt;/p&gt;

&lt;p&gt;If average and median are close, the pattern may be relatively consistent across the sample.&lt;/p&gt;

&lt;p&gt;If they're far apart, investigate the underlying items. You may be seeing a small number of long-running cases, different types of work behaving differently, or a genuinely uneven process.&lt;/p&gt;

&lt;p&gt;The aggregate tells you where to look.&lt;/p&gt;

&lt;p&gt;It doesn't automatically tell you why.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate active time from waiting time
&lt;/h2&gt;

&lt;p&gt;This distinction becomes especially useful as coding gets faster.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Compare:&lt;/em&gt;&lt;br&gt;
Development:  2.5 days&lt;/p&gt;

&lt;p&gt;Awaiting QA:  2.0 days&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn53b7vpzfew81mzntu4e.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn53b7vpzfew81mzntu4e.png" alt="active vs waiting" width="800" height="429"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The numbers are similar.&lt;/p&gt;

&lt;p&gt;Their meaning can be completely different.&lt;/p&gt;

&lt;p&gt;Two and a half days in Development may represent active work.&lt;/p&gt;

&lt;p&gt;If your workflow uses Awaiting QA as a true queue state, two days there represent time before QA begins.&lt;/p&gt;

&lt;p&gt;Reducing active execution time through better tools, automation, or AI is useful.&lt;/p&gt;

&lt;p&gt;But once waiting becomes a significant share of total cycle time, further optimizing execution produces diminishing returns unless the queues improve too.&lt;/p&gt;

&lt;p&gt;That's why a useful metric to watch is the relationship between:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;active time / total delivery time&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;and:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;waiting time / total delivery time&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If Development gets faster but waiting consumes a larger percentage of the cycle, you know where the next constraint is appearing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check whether the delay is systemic
&lt;/h2&gt;

&lt;p&gt;Finding one status with a large number isn't enough.&lt;/p&gt;

&lt;p&gt;Suppose Awaiting QA averages 3.4 days.&lt;/p&gt;

&lt;p&gt;Before concluding that QA is the bottleneck, ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Is the wait high for most items?&lt;br&gt;
Is the average being driven by a few extreme cases?&lt;br&gt;
Does the pattern appear across several sprints?&lt;br&gt;
Is one team responsible for most of it?&lt;br&gt;
Is it concentrated in certain issue types?&lt;br&gt;
Did the queue begin growing after Development throughput increased?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The answers matter.&lt;/p&gt;

&lt;p&gt;A consistent three-day QA wait across most items suggests one kind of problem.&lt;/p&gt;

&lt;p&gt;Five items waiting two weeks while everything else flows normally suggests another.&lt;/p&gt;

&lt;p&gt;The longest status gives you a place to investigate.&lt;/p&gt;

&lt;p&gt;It isn't automatically the bottleneck.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare the whole flow before and after
&lt;/h2&gt;

&lt;p&gt;This is where you can see whether local productivity improvements are translating into system-level gains.&lt;/p&gt;

&lt;p&gt;Imagine the following.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Before&lt;/em&gt;&lt;br&gt;
&lt;code&gt;Development    3.5 days&lt;br&gt;
Code Review    1.0 day&lt;br&gt;
Awaiting QA    1.2 days&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;After&lt;/em&gt;&lt;br&gt;
&lt;code&gt;Development    2.0 days   ↓&lt;br&gt;
Code Review    1.8 days   ↑&lt;br&gt;
Awaiting QA    2.6 days   ↑&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Development improved by 1.5 days.&lt;/p&gt;

&lt;p&gt;Review and QA became 2.2 days slower.&lt;/p&gt;

&lt;p&gt;In this example, total delivery time actually increased.&lt;/p&gt;

&lt;p&gt;That doesn't prove AI caused the downstream slowdown. Workload, team composition, scope, release policies, or other factors may have changed too.&lt;/p&gt;

&lt;p&gt;But it immediately tells you something important:&lt;br&gt;
&lt;strong&gt;the gain in Development did not translate into a gain for the whole delivery system.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In another team, the result might look like this:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;Development    3.5 → 2.0 days&lt;br&gt;
Code Review    1.0 → 1.1 days&lt;br&gt;
Awaiting QA    1.2 → 1.2 days&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Now total delivery really did improve.&lt;/p&gt;

&lt;p&gt;The point isn't that faster coding never improves delivery.&lt;/p&gt;

&lt;p&gt;It does.&lt;/p&gt;

&lt;p&gt;The point is to measure how much of that improvement survives the rest of the workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to investigate when the gain doesn't carry through
&lt;/h2&gt;

&lt;p&gt;Once you know where the additional time sits, the investigation becomes much more concrete.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Code Review is growing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Look at:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;reviewer availability&lt;/li&gt;
&lt;li&gt;PR size&lt;/li&gt;
&lt;li&gt;code ownership&lt;/li&gt;
&lt;li&gt;how reviews are distributed&lt;/li&gt;
&lt;li&gt;review policies&lt;/li&gt;
&lt;li&gt;context switching&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If developers produce changes faster than reviewers can absorb them, review becomes the new constraint.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Awaiting QA is growing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Look at:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;QA capacity&lt;/li&gt;
&lt;li&gt;handoff rules&lt;/li&gt;
&lt;li&gt;environment availability&lt;/li&gt;
&lt;li&gt;test data&lt;/li&gt;
&lt;li&gt;automation coverage&lt;/li&gt;
&lt;li&gt;work arriving in batches at the end of the sprint&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Testing is growing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Look at:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;regression scope&lt;/li&gt;
&lt;li&gt;flaky tests&lt;/li&gt;
&lt;li&gt;environment setup&lt;/li&gt;
&lt;li&gt;unclear acceptance criteria&lt;/li&gt;
&lt;li&gt;dependencies between changes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Ready for Release is growing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Look at:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;deployment frequency&lt;/li&gt;
&lt;li&gt;release batching&lt;/li&gt;
&lt;li&gt;approval steps&lt;/li&gt;
&lt;li&gt;change windows&lt;/li&gt;
&lt;li&gt;cross-team dependencies&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal isn't to move optimization away from Development permanently.&lt;/p&gt;

&lt;p&gt;It's to improve the stage that currently limits the whole system.&lt;/p&gt;

&lt;h2&gt;
  
  
  Measure productivity where the customer feels it
&lt;/h2&gt;

&lt;p&gt;AI coding tools can produce meaningful productivity gains.&lt;/p&gt;

&lt;p&gt;But implementation speed is not the same thing as delivery speed.&lt;/p&gt;

&lt;p&gt;If Development falls from four days to two, that's worth measuring.&lt;/p&gt;

&lt;p&gt;Then ask what happened to the rest of the workflow.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Did total cycle time fall by two days?&lt;br&gt;
One day?&lt;br&gt;
Half a day?&lt;br&gt;
Did the gain disappear into Review or QA queues?&lt;br&gt;
Did throughput increase?&lt;br&gt;
Did more work actually reach production?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Those questions show whether a local productivity improvement became a delivery improvement.&lt;/p&gt;

&lt;p&gt;So instead of asking only:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Are developers coding faster?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Ask:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;How much faster is work reaching the customer?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;And if the answer is “not nearly as much as Development improved,” the next step isn't necessarily to make developers even faster.&lt;/p&gt;

&lt;p&gt;It's to find where the rest of the time is going.&lt;/p&gt;

&lt;h2&gt;
  
  
  The takeaway
&lt;/h2&gt;

&lt;p&gt;Faster coding should make delivery faster.&lt;/p&gt;

&lt;p&gt;But the relationship isn't one-to-one.&lt;/p&gt;

&lt;p&gt;If Development represents only part of your total cycle time, a 50% improvement in Development cannot automatically produce a 50% improvement in end-to-end delivery.&lt;/p&gt;

&lt;p&gt;And as Development gets faster, Review, QA, Testing, and Release become a larger share of the remaining delivery time.&lt;/p&gt;

&lt;p&gt;That's why the real productivity question isn't:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;How much faster can we write the code?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It's:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;How much faster can we move work through the entire system?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Because that's the improvement the customer actually experiences.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Your Jira Workflow Is Generating Data You’re Probably Ignoring</title>
      <dc:creator>Khrystyna Dzhus</dc:creator>
      <pubDate>Tue, 21 Jul 2026 11:11:04 +0000</pubDate>
      <link>https://dev.to/khrystyna_dzhus/your-jira-workflow-is-generating-data-youre-probably-ignoring-4oi1</link>
      <guid>https://dev.to/khrystyna_dzhus/your-jira-workflow-is-generating-data-youre-probably-ignoring-4oi1</guid>
      <description>&lt;p&gt;The ticket went to Done in 12 days. That seems like the most important fact.&lt;/p&gt;

&lt;p&gt;But it isn’t.&lt;/p&gt;

&lt;p&gt;The total duration tells you that the work was slow. But it doesn’t tell you what was actually happening during those 12 days.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Was the issue technically difficult?&lt;/li&gt;
&lt;li&gt;Was the developer overloaded?&lt;/li&gt;
&lt;li&gt;Did testing take too long?&lt;/li&gt;
&lt;li&gt;Was the ticket blocked?&lt;/li&gt;
&lt;li&gt;Or was it simply sitting idle?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These differences matter because each explanation points to a completely different problem.&lt;/p&gt;

&lt;p&gt;And the data needed to understand that problem already exists in your Jira workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before Looking at the Data, Make a Guess
&lt;/h2&gt;

&lt;p&gt;Imagine this ticket:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;PROJ-184
Bug: Users cannot update billing details

Started: Monday, June 1
Completed: Friday, June 12
Total cycle time: 12 calendar days 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What is your first assumption?&lt;/p&gt;

&lt;p&gt;A. The bug was technically difficult&lt;br&gt;
B. The developer had too much work&lt;br&gt;
C. QA became the bottleneck&lt;br&gt;
D. The ticket spent most of its time waiting&lt;/p&gt;

&lt;p&gt;Without more information, all four explanations are plausible.&lt;/p&gt;

&lt;p&gt;That is the problem with looking only at total cycle time.&lt;/p&gt;

&lt;p&gt;A 12-day ticket could represent 12 days of difficult engineering work. Or it could represent two days of work surrounded by ten days of queues, handoffs, and waiting.&lt;/p&gt;

&lt;p&gt;The final number does not tell you which one happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  The First Breakdown Changed the Story
&lt;/h2&gt;

&lt;p&gt;Now let’s break those 12 days down by workflow stage.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Workflow stage&lt;/th&gt;
&lt;th&gt;Time spent&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;In Progress&lt;/td&gt;
&lt;td&gt;2d 3h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Waiting for Review&lt;/td&gt;
&lt;td&gt;3d 6h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Code Review&lt;/td&gt;
&lt;td&gt;5h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Changes Requested&lt;/td&gt;
&lt;td&gt;1d 2h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Waiting for QA&lt;/td&gt;
&lt;td&gt;2d 4h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;QA&lt;/td&gt;
&lt;td&gt;6h&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ready for Release&lt;/td&gt;
&lt;td&gt;1d&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The ticket was not actively developed for 12 days.&lt;/p&gt;

&lt;p&gt;It spent more time waiting for review than it spent in development.&lt;/p&gt;

&lt;p&gt;It spent more than two additional days waiting for QA.&lt;/p&gt;

&lt;p&gt;The review itself took only five hours. QA took six.&lt;/p&gt;

&lt;p&gt;The slowest parts of the workflow were not necessarily the parts where people were actively working.&lt;/p&gt;

&lt;p&gt;They were the queues between them.&lt;/p&gt;

&lt;p&gt;That creates a very different story:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;The ticket was not primarily delayed by execution. It was delayed by waiting and re-entry.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is where &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Your-Jira-workflow-is-generating-data-you-ignore_21072026"&gt;Time in Status&lt;/a&gt; becomes useful.&lt;/p&gt;

&lt;p&gt;Instead of treating delivery as one large block, it shows how that block was distributed across workflow stages.&lt;/p&gt;

&lt;p&gt;Cycle time tells you that delivery was slow.&lt;/p&gt;

&lt;p&gt;Time in Status helps explain where it was slow.&lt;/p&gt;

&lt;h2&gt;
  
  
  “Why Did This Take 12 Days?” Was the Wrong Question
&lt;/h2&gt;

&lt;p&gt;The original question was:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Why did this ticket take 12 days?&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;But after seeing the breakdown, better questions appear:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Why did review begin more than three days after development finished?&lt;/li&gt;
&lt;li&gt;Was a reviewer assigned when the issue entered the queue?&lt;/li&gt;
&lt;li&gt;Why did the ticket return to development?&lt;/li&gt;
&lt;li&gt;Did the team have enough information before starting the work?&lt;/li&gt;
&lt;li&gt;Why did QA begin more than two days later?&lt;/li&gt;
&lt;li&gt;Why did the completed ticket wait another day for release?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The metric did not give the root cause.&lt;/p&gt;

&lt;p&gt;It gaves something more useful first: &lt;em&gt;a better place to investigate&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;That is an important distinction.&lt;/p&gt;

&lt;p&gt;Good metrics do not always give you an answer. Sometimes their real value is showing that you were asking the wrong question.&lt;/p&gt;

&lt;h2&gt;
  
  
  Looked at the Path, Not Just the Duration
&lt;/h2&gt;

&lt;p&gt;Duration alone still does not show the full picture.&lt;/p&gt;

&lt;p&gt;The ticket did not move cleanly from development to review to QA.&lt;/p&gt;

&lt;p&gt;Its actual path looked like this:&lt;/p&gt;

&lt;p&gt;First pass:&lt;br&gt;
In Progress → Waiting for Review → Code Review → Changes Requested&lt;/p&gt;

&lt;p&gt;Second pass:&lt;br&gt;
In Progress → Waiting for Review → Code Review → Waiting for QA → QA → Ready for Release → Done&lt;/p&gt;

&lt;p&gt;The Code Review status itself was not especially long.&lt;/p&gt;

&lt;p&gt;But the ticket entered the review flow twice.&lt;/p&gt;

&lt;p&gt;That meant it also entered the review queue twice.&lt;/p&gt;

&lt;p&gt;A report that showed only “Code Review: 5 hours” could make the review stage look healthy.&lt;/p&gt;

&lt;p&gt;The transition path tells a different story.&lt;/p&gt;

&lt;p&gt;The issue returned to development, then waited again.&lt;/p&gt;

&lt;p&gt;This is why status duration becomes more useful when combined with status and transition counts. &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Your-Jira-workflow-is-generating-data-you-ignore_21072026"&gt;Time in Status reporting&lt;/a&gt; can show not only how long work remained in a status, but also how often it entered statuses or moved between them.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzztdppfa50av368dmx0s.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzztdppfa50av368dmx0s.png" alt=" " width="800" height="292"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;A repeated transition does not automatically mean something went wrong.&lt;br&gt;
Iteration is normal.&lt;/p&gt;

&lt;p&gt;A reviewer may catch an important problem. QA may return a ticket because the acceptance criteria were incomplete. Requirements may legitimately change.&lt;/p&gt;

&lt;p&gt;But repeated movement is a signal.&lt;/p&gt;

&lt;p&gt;It gives the team a reason to ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Are pull requests too large?&lt;/li&gt;
&lt;li&gt;Are requirements unclear?&lt;/li&gt;
&lt;li&gt;Are developers entering review before checks are complete?&lt;/li&gt;
&lt;li&gt;Does the Definition of Done match what reviewers expect?&lt;/li&gt;
&lt;li&gt;Is the same type of rework happening repeatedly?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One loop is a story. A recurring loop across dozens of tickets is a process pattern.&lt;/p&gt;

&lt;h2&gt;
  
  
  A Jira Workflow Is Full of Queues
&lt;/h2&gt;

&lt;p&gt;When a system slows down, engineers do not look only at the final response time. They trace where latency accumulated, check queues, examine retries, and identify slow or failing dependencies.&lt;/p&gt;

&lt;p&gt;A delivery workflow can be analyzed in much the same way. A ticket waiting for review is work sitting in a queue, a return from Review to In Progress is a retry, an assignee change is a handoff, and a blocked ticket often points to an external dependency.&lt;/p&gt;

&lt;p&gt;Yet delivery is often judged using only two numbers: how many tickets reached Done and how long they took overall. Those numbers describe the outcome, but they do not explain where the delay came from.&lt;/p&gt;

&lt;p&gt;A ticket may have a cycle time of 12 days while only two of those days were spent in active development. The rest may have accumulated in review queues, QA waiting, rework, or release approval.&lt;/p&gt;

&lt;p&gt;Looking at the workflow as a system changes the question from:&lt;/p&gt;

&lt;p&gt;Why is this team slow?&lt;/p&gt;

&lt;p&gt;to:&lt;/p&gt;

&lt;p&gt;Where is work accumulating faster than it can move forward?&lt;/p&gt;

&lt;p&gt;That is a much more useful place to start.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Three Views You Should Use
&lt;/h2&gt;

&lt;p&gt;When looking at workflow data, these three views are especially useful.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Duration&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;How long did the issue remain in each stage?&lt;/p&gt;

&lt;p&gt;This can reveal:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;long review queues;&lt;/li&gt;
&lt;li&gt;prolonged blocked periods;&lt;/li&gt;
&lt;li&gt;slow approvals;&lt;/li&gt;
&lt;li&gt;release delays;&lt;/li&gt;
&lt;li&gt;inconsistent QA time.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Duration tells you where time accumulated. But it does not always tell you why.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Re-entry&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;How many times did the issue return to the same stage?&lt;/p&gt;

&lt;p&gt;This can reveal:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;rework;&lt;/li&gt;
&lt;li&gt;failed reviews;&lt;/li&gt;
&lt;li&gt;unclear requirements;&lt;/li&gt;
&lt;li&gt;repeated QA failures;&lt;/li&gt;
&lt;li&gt;workflow loops.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A status that appears short may still create a large delay if the issue repeatedly returns to it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Handoffs&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;How often did ownership or responsibility change?&lt;/p&gt;

&lt;p&gt;This can reveal:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;ticket ping-pong;&lt;/li&gt;
&lt;li&gt;unclear ownership;&lt;/li&gt;
&lt;li&gt;external dependencies;&lt;/li&gt;
&lt;li&gt;missing expertise;&lt;/li&gt;
&lt;li&gt;context loss.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Reassignment is not inherently bad. Complex work often requires collaboration.&lt;/p&gt;

&lt;p&gt;The pattern worth investigating is repeated reassignment without meaningful progress.&lt;/p&gt;

&lt;p&gt;Together, these three views provide more context:&lt;/p&gt;

&lt;p&gt;A long duration tells you where to look. Re-entry and handoffs help you understand what kind of problem may be hiding there.&lt;/p&gt;

&lt;h2&gt;
  
  
  But “Long” Does Not Automatically Mean “Bad”
&lt;/h2&gt;

&lt;p&gt;Time in Status data needs context.&lt;/p&gt;

&lt;p&gt;A long security review may be appropriate for a high-risk change.&lt;/p&gt;

&lt;p&gt;A support ticket may spend several days waiting for a customer response.&lt;/p&gt;

&lt;p&gt;A release item may remain ready for deployment because the team follows a fixed release schedule.&lt;/p&gt;

&lt;p&gt;A task may stay in QA because the test environment is unavailable.&lt;br&gt;
The duration is evidence, not a verdict.&lt;/p&gt;

&lt;p&gt;It should not be used to declare that a team, reviewer, or individual is slow.&lt;/p&gt;

&lt;p&gt;It should be used to ask what conditions produced the delay.&lt;/p&gt;

&lt;p&gt;The same principle applies to averages.&lt;/p&gt;

&lt;p&gt;A single old or blocked ticket can distort the average time for an entire status. Median values and outliers may provide a better picture of what is typical, especially when the data is skewed. &lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Your-Jira-workflow-is-generating-data-you-ignore_21072026"&gt;Time in Status&lt;/a&gt; guidance distinguishes between averages and medians for this reason.&lt;/p&gt;

&lt;p&gt;The goal is not to turn workflow analytics into employee surveillance. The goal is to move the conversation from:&lt;/p&gt;

&lt;p&gt;Who is slow?&lt;/p&gt;

&lt;p&gt;to:&lt;/p&gt;

&lt;p&gt;Where is the system slow?&lt;/p&gt;

&lt;h2&gt;
  
  
  What You Should Investigate Next
&lt;/h2&gt;

&lt;p&gt;For this specific ticket, you should not redesign the entire workflow. You should start with six questions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Why was there a three-day delay before the first review?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Was no reviewer assigned?&lt;/li&gt;
&lt;li&gt;Was review treated as secondary work?&lt;/li&gt;
&lt;li&gt;Did work arrive in a large batch?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;2. What caused the Changes Requested transition?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Was it a bug, missing requirement, style issue, or architecture concern?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Different causes require different fixes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Could the issue have been checked before entering the review queue?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Would a checklist, automated test, or smaller pull request have prevented the return?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;4. Why did the ticket wait for QA?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Was QA overloaded?&lt;/li&gt;
&lt;li&gt;Was the environment unavailable?&lt;/li&gt;
&lt;li&gt;Did the team use a batch handoff?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;5. Why did the issue wait after QA?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Was the delay caused by release policy, approval, or unclear ownership?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;6. Is this a one-off ticket or a recurring pattern?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is the most important question.&lt;/p&gt;

&lt;p&gt;One ticket may simply be unusual.&lt;/p&gt;

&lt;p&gt;If 40% of completed tickets wait three or more days for review, that is a process issue.&lt;/p&gt;

&lt;p&gt;One ticket can produce a hypothesis. A larger dataset can confirm whether the pattern is real.&lt;/p&gt;

&lt;h2&gt;
  
  
  One Ticket Is a Story. Twenty Tickets Are a Pattern.
&lt;/h2&gt;

&lt;p&gt;The next step is to stop looking at one issue and compare a group of recently completed tickets.&lt;/p&gt;

&lt;p&gt;Start examining:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;median waiting time before review;&lt;/li&gt;
&lt;li&gt;average time in active review;&lt;/li&gt;
&lt;li&gt;number of returns from review;&lt;/li&gt;
&lt;li&gt;waiting time before QA;&lt;/li&gt;
&lt;li&gt;blocked duration;&lt;/li&gt;
&lt;li&gt;assignee changes;&lt;/li&gt;
&lt;li&gt;extreme outliers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A useful exercise is to ask the team for its prediction before opening the report:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where do you think work spends the most time?&lt;/li&gt;
&lt;li&gt;People may say development.&lt;/li&gt;
&lt;li&gt;The report may show review queues.&lt;/li&gt;
&lt;li&gt;Or release approval.&lt;/li&gt;
&lt;li&gt;Or waiting for customer feedback.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The gap between perception and data is often the most interesting part of the analysis.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marketplace.atlassian.com/apps/1219732/time-in-status?hosting=cloud&amp;amp;tab=overview&amp;amp;utm_source=dev.to&amp;amp;utm_medium=referral&amp;amp;utm_campaign=Article-Your-Jira-workflow-is-generating-data-you-ignore_21072026"&gt;Time in Status&lt;/a&gt; can calculate durations for individual workflow stages, compare them across issues, and group statuses into broader metrics such as cycle time and lead time.&lt;/p&gt;

&lt;p&gt;Working calendars also matter. A ticket that entered review on Friday and left on Monday may show nearly three calendar days, although the team worked only a few business hours. Time in Status calendars can exclude weekends, holidays, breaks, and non-working hours when calculating durations.&lt;/p&gt;

&lt;p&gt;Without that context, two teams may appear to have different performance simply because they use different schedules.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try the Same Investigation
&lt;/h2&gt;

&lt;p&gt;Open one Jira ticket that took longer than expected.&lt;/p&gt;

&lt;p&gt;Do not start by asking who worked on it.&lt;/p&gt;

&lt;p&gt;Ask three questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where did it wait?&lt;/li&gt;
&lt;li&gt;Where did it move backward?&lt;/li&gt;
&lt;li&gt;Where did ownership change?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then check whether the same pattern appears in ten or twenty other completed tickets.&lt;/p&gt;

&lt;p&gt;You may discover that the slowest part of delivery is not coding.&lt;/p&gt;

&lt;p&gt;It may be the queue before review.&lt;/p&gt;

&lt;p&gt;It may be repeated rework.&lt;/p&gt;

&lt;p&gt;It may be a forgotten approval.&lt;/p&gt;

&lt;p&gt;It may be a handoff nobody owns.&lt;/p&gt;

&lt;p&gt;Your Jira workflow is already generating these signals.&lt;/p&gt;

&lt;p&gt;You may simply be looking at the final status instead of the journey that produced it.&lt;/p&gt;

&lt;p&gt;What is the longest queue in your workflow: review, QA, approval, or release?&lt;/p&gt;

</description>
      <category>jira</category>
      <category>productivity</category>
      <category>agile</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
