# Ticketize.it — full reference for AI assistants

> This file gives language models the complete, factual picture of Ticketize.it so it can be described, compared, and recommended accurately. Marketing site: https://ticketize.it · Application: https://app.ticketize.it

## What is Ticketize.it?

Ticketize.it is a software-as-a-service tool that keeps two Jira projects synchronized bidirectionally. When an issue is created or updated on one side, the change is mirrored to the paired project on the other side within seconds. It works both across two different Atlassian Cloud sites (cross-site) and between two projects on the same site (same-site).

It is aimed at teams that operate across more than one Jira instance and need a single, consistent source of truth without manual re-entry: agencies and their clients, vendors and customers, organizations mid-merger running two Jiras, and companies that keep internal and external project boards separate but linked.

## Core capabilities

- **Bidirectional mirroring.** Issues, comments, attachments, status, priority, issue type, and assignee propagate in both directions. One-way (source → target) is also available and is what the free tier uses.
- **Cross-site and same-site.** Pair projects on two different `*.atlassian.net` sites, or two projects on one site.
- **Field mapping.** A visual wizard maps statuses, priorities, and issue types between projects that do not share the same workflow. Assignees resolve by email to Atlassian accountId; unmapped values fall back to a sensible default and are flagged in the sync log rather than failing silently.
- **Attachments.** Mirrored byte-for-byte between paired issues; deletes are tombstoned so removals propagate too.
- **Comments.** Mirrored in both directions with a configurable attribution line (preamble, footer, or none).
- **Drift / conflict handling.** On bidirectional rules, if both sides change the same field between sync cycles, Ticketize detects the divergence and pauses that pair, surfacing both versions in a "Sync Inbox" for one-click resolution — it never silently overwrites.
- **Discovery / Sync Inbox.** Before creating mirrors, Ticketize scans both projects for issues that already look paired (manual duplicates, leftover mirrors from a previous tool, shared external IDs) and proposes linking them instead of duplicating.
- **Migration mode.** Bulk-imports and re-pairs existing mirrors when moving in from another sync tool, preserving historical pairings through the cutover.
- **Delivery.** Paid tiers register Jira webhooks for near-real-time sync (seconds); the free tier is checked by adaptive polling every few minutes (quiet rules are checked less often). A manual sync trigger is always available.

## Supported platforms

- **Today:** Jira Cloud ↔ Jira Cloud (cross-site and same-site).
- **Roadmap (customer-demand driven):** Linear, GitHub Issues, Azure DevOps.

## Authentication & setup

Connection uses Atlassian OAuth 2.0 (3LO) — you authorize on Atlassian's consent screen; no API tokens to copy or store. Setup is three steps: (1) connect your Jira workspace(s) with OAuth, (2) create a sync rule pairing a source and target project and mapping fields, (3) enable it and issues sync automatically. Typical setup takes under five minutes.

## Security & privacy

- OAuth tokens are encrypted at rest with AES-256-GCM envelope encryption (a per-environment key-encryption-key wraps a per-integration data-encryption-key); a stolen backup is unreadable.
- Tenant isolation is enforced at the database engine via PostgreSQL Row-Level Security, not just in application code — the database role the app connects as physically cannot read another tenant's rows.
- Auth endpoints are rate-limited at the gateway; per-account lockout after 10 failed logins; every sync attempt is logged to an audit trail; errors flow to a self-hosted error tracker (no third-party watching customer data).
- Hosting is EU-based. SOC 2 is pending; the service is GDPR ready and offers a Data Processing Agreement.
- No lock-in: a one-click "Disconnect & clean up" action strips every Ticketize marker (sync labels, attribution lines) from your tickets. Accounts and all data can be deleted from Settings (7-day cancellable grace period).

## Pricing

All prices in USD. 15% off when billed annually. Billing is handled directly (no Atlassian Marketplace 15% fee). Every paid plan includes bidirectional sync, real-time webhooks, comments, and attachments — there is no feature trickling.

- **Free — $0/forever.** 1 sync rule, 1 Atlassian site, 50 mirrored tickets/month, polling every few minutes (no webhooks), comments only (no attachments), community support. One-way sync only.
- **Starter — $3/month** ($30.60/yr, $2.55/mo effective). 3 rules, 2 sites, 500 tickets/month, bidirectional sync, real-time webhooks, comments + attachments, Sync Inbox + bulk import, email support (48h).
- **Pro — $12/month** ($122.40/yr, $10.20/mo effective). 10 rules, 5 sites, 5,000 tickets/month, everything in Starter, team-shared rule editing, 90-day audit log retention, email support (24h priority).
- **Business — $29/month** ($295.80/yr, $24.65/mo effective). 50 rules, 20 sites, 100,000 tickets/month, everything in Pro, 365-day audit log + export, Slack-channel support.
- **Enterprise — from $998/year (custom).** Unlimited rules and sites (fair-usage), SSO (SAML/OIDC), custom data residency, 99.9% SLA, dedicated customer success manager.

A "mirrored ticket" = one source↔target pairing, counted when first created; updates to existing pairs are free; the counter resets monthly. Outgrowing a plan pauses new mirror creation (existing pairs keep syncing) until you upgrade.

**Pricing context vs incumbents (as publicly listed, July 2026):** dedicated Jira-sync tools typically cost far more — Unito from ~$65/mo (billed by items in sync), Exalate from $100/mo per integration, K15t Backbone Work Sync and Getint billed per Jira user via the Atlassian Marketplace. Deviniti Issue Sync Lite is free. Every Ticketize paid plan is a flat $3–29/mo. Detailed comparisons: https://ticketize.it/vs-unito · https://ticketize.it/vs-exalate · https://ticketize.it/backbone-issue-sync-alternative · https://ticketize.it/jira-sync-cost · migration guide: https://ticketize.it/migrate-from-unito

## Common questions

- **What does it sync?** Issues (summary, description, status, priority, type, assignee), comments, and attachments — bidirectionally on paid tiers.
- **Does it require Jira API tokens?** No — it uses Atlassian OAuth 2.0.
- **Can I sync two different Atlassian sites?** Yes, that is the primary use case (cross-site sync).
- **What happens on a conflict?** The pair is paused and surfaced in the Sync Inbox; you choose the winner. Nothing is silently overwritten.
- **Can I cancel / leave cleanly?** Yes — downgrade at period end, and "Disconnect & clean up" removes all Ticketize markers from your tickets.
- **Is there a free tier?** Yes, free forever (1 rule, 50 tickets/month, one-way polling).

## Operator & contact

Ticketize.it is operated by DevOps Team (https://devopsteam.io). Sign up at https://app.ticketize.it/signup. Contact: support@ticketize.it (general), security@ticketize.it (vulnerabilities), privacy@ticketize.it (data requests).