Problem Statement
On the Releases list page, the crash-free-rate column shows a health indicator (fire for critical, yellow warning, green check), but the thresholds are hardcoded (fire below 98%, warning below 99.5% in releaseCardProjectRow.tsx). Teams with different reliability targets can't align it to their own goals. Crash-rate metric Alerts already let a team configure critical/warning thresholds, but those only notify whoever set them up. Customers want the passive Releases-page indicator to reflect their own target so anyone viewing a release in the UI can tell at a glance whether it's healthy.
Solution Brainstorm
Let orgs/projects configure the crash-free-rate thresholds driving the Releases-page indicator (a critical threshold for the fire icon, a target threshold for the warning icon), ideally reusing the existing Release Thresholds concept (crash_free_session_rate / crash_free_user_rate).
Product Area
Releases
Problem Statement
On the Releases list page, the crash-free-rate column shows a health indicator (fire for critical, yellow warning, green check), but the thresholds are hardcoded (fire below 98%, warning below 99.5% in releaseCardProjectRow.tsx). Teams with different reliability targets can't align it to their own goals. Crash-rate metric Alerts already let a team configure critical/warning thresholds, but those only notify whoever set them up. Customers want the passive Releases-page indicator to reflect their own target so anyone viewing a release in the UI can tell at a glance whether it's healthy.
Solution Brainstorm
Let orgs/projects configure the crash-free-rate thresholds driving the Releases-page indicator (a critical threshold for the fire icon, a target threshold for the warning icon), ideally reusing the existing Release Thresholds concept (crash_free_session_rate / crash_free_user_rate).
Product Area
Releases