# Bi-directional ticket sync

GLOSSARY, read 10 Nov 2026

**Definition.** Bi-directional ticket sync keeps a remediation ticket in an IT service tool and its finding in the vulnerability platform in step: status changes in either place update the other. A fix closed by IT can trigger re-verification, and a finding closed by a rescan can close the ticket.

One-way ticket creation leaves two systems to reconcile by hand. Check which fields sync, how conflicts resolve, and what happens when a ticket is canceled.

Jira and ServiceNow are the usual pair. Ask about any other system before purchase.

## A sourced example

On 2026-11-10 Brinqa's ticket sync documentation covered syncing Brinqa tickets with outside ticketing systems such as ManageEngine, Jira or ServiceNow.

## Related terms

- [Owner assignment](/glossary/owner-assignment/)
- [Remediation grouping](/glossary/remediation-grouping/)
- [Remediation SLA](/glossary/remediation-sla/)
- [Connector](/glossary/connector/)

## Sources

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

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/bi-directional-ticket-sync/
