# ticket re-linking

GLOSSARY, read 10 Nov 2026

**Definition.** Ticket re-linking reconnects open findings to the tickets already raised for them, so the new platform does not open duplicates. Brinqa documents a ticket sync automation for Jira that you run and then check under Remediation, Tickets, filtered by source. Kenna's API has endpoints that return fixes in a ServiceNow format.

Match on the ticket key and the finding or asset it covers. Run the sync in a test project first and compare the ticket counts before and after, since a duplicate wave lands on the same teams who read your SLA reports.

Decide who closes the old tickets and when. Leaving them open after cutover inflates the backlog.

## A sourced example

Brinqa's ticket sync documentation walks through launching the Jira ticket sync automation and viewing tickets by source, and Kenna's reference lists ServiceNow List Fixes and ServiceNow Search Vulnerabilities.

## Related terms

- [SLA carry-over](/glossary/sla-carry-over/)
- [connector parity](/glossary/connector-parity/)
- [asset identity matching](/glossary/asset-identity-matching/)
- [exception carry-over](/glossary/exception-carry-over/)

## Sources

- Source for the example: ticket re-linking: https://docs.brinqa.com/docs/ticket-sync (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/ticket-re-linking/
