Reworked Tasks counts items that moved backward in the workflow — for example, from "In Review" back to "In Progress." It's a direct signal of quality issues, requirements churn, or weak review processes.
What it measures
From the live tooltip: "Tasks that moved backward in the workflow, indicating revisions or corrections were needed. Signals quality or requirement issues. High rework rates may indicate lack of clarity or weak review processes."
"Backward" is determined by your status mapping — the order you've configured for each integration's statuses inside Administration → Productivity Tools. A transition is counted as rework when it goes from a later status to an earlier one in that order.
How to interpret it
Steady, low number — healthy. Some rework is normal in any creative workflow.
Climbing trend — signals quality erosion, unclear requirements, or test-coverage gaps.
Concentrated in one issue type (for example, all bug fixes) — that segment of work specifically needs attention.
What to do about it
Strengthen definition-of-ready so requirements are clearer before work starts.
Tighten definition-of-done with explicit testing and acceptance criteria.
Investigate whether reviewers can catch issues earlier — long-cycle reviews tend to surface rework late.
If the trend coincides with a status-mapping change, double-check that the new mapping reflects forward progress correctly.
Related metrics
Cycle Time
Change Failure Rate
Sprint Efficiency