We’re introducing a new Flow Efficiency breakdown by issue type (e.g., Task, Bug, Story, Improvement) to help teams understand where their time and effort are being invested — and whether technical debt is consuming too much capacity.

Key Capabilities:

Efficiency by Issue Type:

Analyze flow efficiency separately for Bugs, Tasks, Stories, and other custom issue types.

Technical Debt Awareness:

Identify trends such as excessive time spent on bugs or rework, highlighting technical debt accumulation over time.

Effort Investment Insights:

Visualize how engineering time is split across planned work vs. unplanned fixes or support tasks.

Use Cases:

Detect if reactive work (bugs, support) is slowing down feature delivery

Justify refactoring or tech debt reduction efforts

Improve planning balance between innovation and maintenance

User Value:

Empowers engineering leaders to make data-driven decisions about resource allocation, tech debt prioritization, and workflow stability.