Portfolio Issue Type Mix(4.1.7)

A project that is 70% Bugs is spending most of its capacity on remediation, not value delivery. A project that is 90% Epics may be in a planning phase with little execution happening. The issue type mix tells you what kind of work each team is actually doing — which may or may not match what leadership believes they are focused on.

What you can conclude

• A project dominated by Bugs is a quality signal — something is generating a disproportionate amount of defect work relative to feature work.
• A project with a balanced mix of Tasks, Stories, and Epics is in a healthy delivery rhythm.
• A portfolio-wide shift toward more Bugs over time is an early warning of technical debt accumulation across the organization.

How this chart works

Stacked 100% bar chart showing the proportion of each issue type per project. Each issue counts once over the complete weeks of the selected range, however many of those weeks it was active in, under the type it carried at its latest activity in that range: an issue whose type changed counts only under that latest type, and an issue that moved to another project counts once in each project where it recorded activity in that range. Use the date and project filters to compare specific periods.

The week in progress is not counted: only complete weeks enter the chart, and a project with no complete week in the selected range has no bar.