Issue Exclusion

Issue metrics are easily distorted by a small number of extreme tickets — an epic left open for eight months, a bug reopened and forgotten, a sub-task that was never meant to be tracked. Issue Exclusion gives you two ways to keep those out of your numbers: excluding whole issue types, and setting outlier thresholds per metric.

Excluded Issue Types

Issues matching these types are excluded at the source during sync and will never appear in any metrics, reports, or dashboards.

Select from the issue types Waydev has discovered in your connected trackers, or type a name and click Add to exclude a type that hasn't been synced yet — useful when you know a type exists but hasn't appeared in your data. Currently excluded types are listed below the field as removable badges.

This is the strongest form of exclusion: the data is dropped rather than filtered, so it doesn't reappear anywhere. Typical candidates are sub-tasks, which would otherwise double-count work already captured by their parent, and administrative or placeholder types that don't represent delivery work.

Outlier thresholds

Each threshold is expressed in days, and each applies only to its own metric. An issue that exceeds the cycle time threshold is dropped from cycle time calculations but still counts everywhere else — unlike an excluded issue type, which disappears entirely.

Issues at or above a threshold are excluded from that metric's calculations. Leave a field blank to disable the threshold, in which case nothing is excluded from that metric.

• Cycle Time outlier threshold — Issues whose cycle time reaches this value are excluded from cycle time calculations.
• Issue → PR Time outlier threshold — Issues whose time to first linked pull request reaches this value are excluded from issue-to-PR time calculations. Catches tickets that sat in the backlog long before anyone started coding.
• Bug Resolution Time outlier threshold — Bugs whose resolution time reaches this value are excluded from bug resolution time calculations.
• Open Bug Age outlier threshold — Open bugs whose age reaches this value are excluded from open bug age calculations. Useful for keeping long-abandoned bugs from inflating your backlog age.
• Critical Bug Resolution Time outlier threshold — Critical bugs whose resolution time reaches this value are excluded from critical bug resolution time calculations.
• Time in QA outlier threshold — Tickets whose time in the QA stage reaches this value are excluded from QA time calculations.