Your engineers plan from a tracker, not from a security dashboard. A ticket integration keeps one ticket per FortWatch issue in the tracker you choose, and keeps the two in sync both ways. Workspace owners and admins connect them from Integrations → Tickets; integrations are part of the Pro plan and above, and of the trial.

Supported Trackers

Jira Cloud — a Jira issue in the project and issue type you route to. FortWatch acts as the Atlassian account that connects it, so a dedicated bot account keeps the history clear. Jira integration
Linear — an issue in a team, a project in it, or a new project FortWatch creates, written by the FortWatch app user and labeled FortWatch. A Linear admin installs the app. Linear integration
Notion — a page in the database you choose, or in one FortWatch creates with the right columns. Notion integration
WebWork — a task in the WebWork project you route to, or in a new project FortWatch creates. Connect as a WebWork Owner or Executive Manager, with OAuth or a personal access token.

Set It Up

Connect the tracker and approve FortWatch on its consent screen.
Routing — send the whole workspace, a FortWatch project or one asset to a project, team or database. The most specific route wins.
Field mapping — FortWatch pre-fills the title, the description with the fix, the priority from severity, the assignee by email, the due date from the SLA and a link back. Check which statuses mean fixed, reopened and dismissed.
Sync options — whether tickets are created automatically, the minimum severity, whether an asset's first scan creates tickets, a daily cap (25 by default), what happens on a fix or a dismissal (close the ticket, or only comment), and comments both ways.
Click Finish, then Run test: FortWatch creates a sample ticket, comments on it and closes it, so you see it work end to end.

To file what is already open, use Send existing open issues: it sends every open issue your routes cover, a day's cap at a time.

What Stays in Sync

A fix a scan confirms closes the ticket with a comment naming the scan; a teammate marking the issue fixed closes it with their name.
A problem that comes back reopens the same ticket, with a comment.
A dismissal closes the ticket with the reason, or only comments, as you chose.
A severity change updates the priority.
Comments flow both ways, marked with who wrote them.

When Someone Marks a Ticket Done

Moving a ticket to done tells FortWatch someone believes the issue is fixed, so FortWatch rescans the issue's asset. If the problem is gone, the issue closes. If it is still there, the ticket is reopened once with the evidence; after that FortWatch only comments, so it never fights a person. The scan, not the ticket, decides whether the issue is resolved. Where the tracker has a won't-do status, using it suggests a dismissal in FortWatch; it never dismisses on its own.

The Sync Log

Each connection keeps a log of every push and every change it read back, with the result. A failed operation can be sent again from the log. If the tracker stops accepting FortWatch (a revoked grant, a removed member), the connection asks to be reconnected and catches up once it is.

← Previous

Alerts in Slack and Signed Webhooks