Ticketing Integrations

RedVeil integrates with external issue trackers so security findings flow directly into your team's existing workflow. Connect Jira or Linear, and RedVeil will create, link, and close tickets on your behalf — no copy-pasting required.

Supported Providers

Getting Started

Prerequisites

• You must be an organization admin to manage integrations.

Connecting a Provider

1. Navigate to Settings > Integrations.
2. Toggle the switch next to the provider you want to connect.
3. For Jira: you will be prompted to enter your Atlassian subdomain (e.g. acme for acme.atlassian.net). This is optional — leave it blank to auto-select.
4. Complete the authorization flow in the popup window.
5. Once authorized, the provider card will show a green LINKED status indicator.

Disconnecting a Provider

1. Open Settings > Integrations and click the Config button on the provider card.
2. In the configuration dialog, click Disconnect.
3. The connection is revoked and the provider returns to OFFLINE status.

Features

Manual Ticket Creation

From any finding's detail page, use the actions menu (three-dot icon) and select Create External Ticket. RedVeil will create a ticket in every connected provider and link it back to the finding. The ticket includes:

• Finding title as the ticket summary
• Severity rating
• Affected asset
• Full description
• A direct link back to the finding in RedVeil

Created tickets appear in the External Tickets section at the bottom of the finding detail page, with clickable links that open directly in Jira or Linear.

Automatic Ticket Creation

When enabled, RedVeil automatically creates an external ticket every time a new finding is discovered during a pentest. Toggle this per-provider:

1. Go to Settings > Integrations and click Config on the provider.
2. Enable Auto-create tickets.
3. Save changes.

Any finding created after this point — whether from automated scanning or manual host assessment — will have a corresponding ticket created automatically.

Auto-Close on Remediation

When a finding passes a remediation retest, RedVeil can automatically transition the linked external ticket to a closed/done status. Toggle this per-provider:

1. Open the provider's Config dialog.
2. Enable Close on remediation pass.
3. Save changes.

RedVeil resolves the correct "closed" transition for your project:

• Jira: transitions the issue through your workflow, matching against status names like "Done", "Resolved", or "Closed".
• Linear: moves the issue to the team's completed state, falling back to states named "Done", "Resolved", or "Closed".

Advanced Configuration

Open the Advanced section in the provider configuration dialog to customize status mapping.

Initial Status

Set the status name that newly created tickets should be assigned. For example:

• Jira: To Do, Open, Backlog
• Linear: Todo, Backlog, Triage

If left blank, RedVeil uses sensible defaults (Jira uses the project's default workflow start; Linear uses the first "unstarted" state).

Close Status

Override the status name that RedVeil uses when closing tickets after remediation. For example:

• Jira: Done, Resolved, Fixed
• Linear: Done, Closed

If left blank, RedVeil matches against common closed-state keywords: "done", "resolved", "closed", "fixed", "complete".

Viewing External Tickets

Finding Detail Page

Each finding displays its linked external tickets in an External Tickets section. Each ticket shows:

• The provider icon (Jira or Linear)
• The ticket key or ID (e.g. PROJ-123 for Jira, ENG-42 for Linear)
• The provider name and current status
• A clickable link that opens the ticket in the external system

Permissions

• Admin-only: All integration management (connect, disconnect, configure, create tickets) requires organization admin privileges. Non-admin users can view linked tickets on findings but cannot create or manage them.
• Organization-scoped: Each integration connection is scoped to your organization. Findings and tickets are fully isolated between organizations.

Troubleshooting

FAQ

Can I connect both Jira and Linear at the same time?

Yes. Each provider is independent. Enabling auto-create on both will create a ticket in each system for every new finding.

What happens to existing tickets if I disconnect a provider?

Existing ticket links remain visible on findings for audit purposes. No further sync operations (e.g. auto-close) will occur for the disconnected provider.

Can I change the Jira site after connecting?

Yes. Open the Jira Config dialog, click Reconnect, and enter the new subdomain. You will need to re-authorize.

Which Jira deployment types are supported?

Jira Cloud is fully supported today. Jira Data Center (self-managed) is available on request — contact support.