Skip to main content
Ticket replication keeps tickets synchronized between Ravenna and external ticketing systems. When enabled, tickets are automatically replicated in both directions to maintain consistency across platforms.

How it works

Ticket replication provides bidirectional synchronization between Ravenna and external systems:

Ravenna → External System

  • New tickets created in Ravenna can automatically create corresponding tickets in external systems
  • Updates to ticket status, priority, assignees, and comments sync to external systems
  • Maintains links between Ravenna tickets and their external counterparts

Ravenna ← External System

  • Webhooks from external systems automatically update linked Ravenna tickets
  • Changes to status, comments, and assignments flow back to Ravenna
  • Preserves ticket history and context during synchronization

Prerequisites

Before enabling ticket replication, ensure you have:

Configuration

Queue-level settings

Ticket replication is configured per queue in your queue settings:
1

Navigate to queue settings

  1. Go to Queues in your workspace
  2. Select the queue you want to configure
  3. Click the Settings tab
2

Configure ticket replication

  1. Click Ticket Replication in the left sidebar menu
  2. You’ll see options for each connected integration
  3. Configure the replication direction for each integration:
    • Ravenna → [Integration]: Replicate new Ravenna tickets to the external system
    • [Integration] → Ravenna: Replicate external tickets to Ravenna via webhooks
3

Save your settings

Toggle the desired replication options and settings will be saved automatically

Supported integrations

Ticket replication is currently available for:
https://mintcdn.com/ravenna/sHkIxR1kZRcsw3Gd/icons/linear.svg?fit=max&auto=format&n=sHkIxR1kZRcsw3Gd&q=85&s=050100e23ca2c22c12d3a01ea83845c4

Linear

Issues, projects, teams, and workflow states

Troubleshooting

Cause: Integration disconnectedSolution:
  • Check integration connection status in Settings > Integrations
  • Try disconnecting and reconnecting the integration
Cause: Only one replication direction enabledSolution:
  • Verify both replication toggles are enabled in queue settings

Best practices

Start with one direction: Enable Ravenna → Linear first to test the integration before enabling bidirectional sync. Monitor initial sync: Watch the first few replicated tickets to ensure field mapping works as expected. Use consistent workflows: Align status workflows between Ravenna and Linear for smoother synchronization.