The Catalog Issues page is a critical surface in Traceable where security teams monitor vulnerabilities and compliance issues detected across API endpoints through Live Traffic, AST, and Compliance policies.
As customers scaled their API footprint, the Issues page became increasingly noisy and difficult to act upon. This project focused on redesigning the experience to help users understand their security posture at a glance, prioritize critical issues, and take action at scale.
The Issues page was meant to help teams assess risk, prioritize fixes, and track progress. But it fell short on all three resulting in the following key problems:
<aside> 1ď¸âŁ No clear sense of priority
The page didnât answer a basic question âWhat should I fix first?â. Issues werenât ordered by severity, there were no trend signals, and teams couldnât tell if security was improving or getting worse.
</aside>
<aside> 2ď¸âŁ Confusing issue data representation
Issues were grouped by default, but this wasnât obvious. As a result, metrics showed thousands of issues while the table showed only a few rows, making the data feel unreliable and confusing.
</aside>
<aside> 3ď¸âŁ Too much manual work
Users couldnât take action at scale. Marking issues, reducing noise, or creating Jira tickets had to be done one-by-one, which didnât match real security workflows.
</aside>
<aside> 4ď¸âŁ Rigid severity model
Severity was fixed per issue type. But in reality, the same issue can be low risk for internal APIs and high risk for public ones, something the product couldnât handle.
</aside>