Convert security findings into engineering tickets directly from Krait-quickly and with full context. Each ticket carries all the essential details, including metadata, affected code, and cloud assets, so engineers can take action without chasing information. This keeps security and engineering teams aligned and makes the entire remediation process smoother, whether you’re operating day-to-day or at enterprise scale.
The Tickets Dashboard provides a unified, real-time view of all tickets generated within your Krait workspace-whether created through Jira or Linear. This dashboard enables security teams, engineering teams, and cross-functional stakeholders to track remediation progress with clarity and precision.This section explains the layout, features, and user interactions available within the dashboard.
Each row in the dashboard represents a single ticket enriched with contextual metadata. The interface is designed for clarity and efficient scanning, making it easy to assess remediation status at a glance.
Title & Ticket Key
Shows the issue title along with the ticket identifier (e.g., TES-13, KRA-256). Each entry includes a link to open the issue directly in Jira or Linear.
Resource Context
Indicates where the vulnerability originated-Repository, Container, Cloud, Mobile App (APK), DNS, or API Inventory-allowing engineers to immediately understand scope and impact.
Status
Displays the current workflow stage (Backlog, Todo, In Progress, Done, etc.). Status is continuously synced from your ticketing platform to keep Krait aligned with engineering activity.
Priority
A color-coded badge (Critical, High, Medium, Low) that helps teams quickly prioritize remediation tasks.
Project
Shows the associated Jira or Linear project/team where the issue is tracked.
Assigned To
Displays the engineer currently responsible for the remediation, with avatars for quick visual identification.
System
Identifies the originating ticketing platform (Jira or Linear) - through recognizable platform icons.