Sprints and planning · Taskending editorial team
Find issues that are stuck in the same status
Status age describes time in the current stage. A recently edited old issue has not necessarily just entered that stage.
Updated: · 1 min read
How to apply it
Separate the last status-transition time from the general update timestamp when reading Taskending reports. Open the longest-waiting issues and inspect the last meaningful progress. Clarify the owner, blocker and next review time.
A concrete example
An issue may have waited in review for five days and received a new label today. Its general update is recent, but its review wait remains five days. That distinction prevents unrelated edits from hiding a bottleneck.
What to watch for
Long waits are not always mistakes. Customer approval or an external dependency may justify them, but the reason and follow-up owner should be visible. Respect limits where historical transition data is unavailable.
How to check the outcome
Review the oldest records regularly. At the next review, the reason a record is still waiting should be understandable.
Try it in your own workflow.
Create a company workspace and your first issue. Taskending is currently free.
Start for free