Idle Issues (Jira, Trello)
Development projects running smoothly start with a healthy pipe progressing well at the level of the issues. A blocked issues pipeline will cascade down to all development activities, generating series of undesired effects. In today's fast-paced development world, it has become crucial for developers, their teams and managers to identify rapidly issues that are not progressing, uncover the cause and solve the bottleneck. This is where the Idle Issues report is critically important in helping fastrack the discovery of stalled issues, and their resolution.
Identify Stalled Issues and Uncover Blockers
with the
Idle Issues (Jira, Trello)
Development projects running smoothly start with a healthy pipe progressing well at the level of the issues. A blocked issues pipeline will cascade down to all development activities, generating series of undesired effects. In today's fast-paced development world, it has become crucial for developers, their teams and managers to identify rapidly issues that are not progressing, uncover the cause and solve the bottleneck. This is where the Idle Issues report is critically important in helping fastrack the discovery of stalled issues, and their resolution.
From startups to large enterprises, Keypup serves all the unique complexities related to project size, structure and teams, including:
What is the Idle Issues Report?
This report lists all Jira or Trello issues that idled in a given workflow status and that were not updated recently, over the selected time period (e.g. 12 months).
Status names in the insight can be changed to match your specific Jira/Trello definitions.
By tracking issues that idle in a specific workflow status, you can identify and resolve bottlenecks at issue level. You can now access instantly a list of issues to identify blockers and set a course of action to remove them and sanitize your projects along the way.
How to improve on this metric?
- Locate bottlenecks in engineers’ plannings:
- Use the Value Stream Management dashboard to understand your engineering habits and patterns and optimize your resources allocation, and added-value
- Use the Sprint overview dashboard to assess your engineering team’s planning and activity.
- Ensure the scope of tasks is clear as missing or vague specifications can generate scope creeps creating delays and stalling. Unclear scope can lead to issues handling being delayed if the assignee meets blockers or difficulties.
- Ensure the issue was properly integrated into a sprint or a batch of work. Issue remainders must be addressed and thoroughfully integrated to follow-up batches to avoid being lost in the development pipe.