Tickets in GitHub, Jira or Linear
Exploited or severe vulnerabilities become tickets, by hand or on their own, and are updated once dealt with.
On the Pro and Consultant plans, Provetry can open tickets in your tracker, so vulnerabilities reach the people who fix them.
- In Alerts › Tickets in your tracker, connect GitHub (a repository and a fine-grained token with Issues: Read and write), Jira Cloud (site, project key, account e-mail, API token) or Linear (team key, personal API key).
- Provetry checks the connection at once.
- Choose Make automatic to open tickets on their own, from the level you choose (exploited vulnerabilities, or above a severity). Otherwise, open them on request from a vulnerability.
A ticket gets a comment once the vulnerability is assessed as not affected or fixed, or is no longer in a supported release; on GitHub it is also closed. Vulnerabilities already listed when you connect the tracker get a ticket on request, except exploited ones, which get one at once. Tokens are encrypted, used only to open and comment tickets, and never shown again. Removing a tracker leaves its tickets where they are.
Still stuck? Write to us at hello@provetry.com.