> ## Documentation Index > Fetch the complete documentation index at: https://docs.woes.dev/llms.txt > Use this file to discover all available pages before exploring further. # Jira Connector > Link Woes support issues to Jira — create issues from support work and sync status back to engineering. # Jira Connector Jira logo Jira is the live engineering-ticket connector for Woes. It lets support move a technical issue into Atlassian without losing customer context, and keeps the linked Jira ticket in step as the support issue progresses. ## At A Glance | Use Jira for | Where it appears | | ---------------------------------------------------------------------------- | -------------------------------------- | | Moving bugs, docs gaps, and technical follow-up from support into Atlassian. | Integrations, Issues, and Automations. | ## What it does * **Connect a Jira site** from **Workspace Settings → Integrations → Jira**. * **Pick a default project.** In the Jira card's manage dialog, choose the Jira project new issues are created in. * **Create a Jira issue from a support issue.** Open a support issue's detail drawer and choose **Create Jira issue**. Woes creates the ticket in your default project from the issue's summary and description, then links the two records. * **Jump to the ticket.** Once linked, the issue shows **View in Jira** with the Jira key and a direct link. * **Status sync (Woes → Jira).** When a linked support issue changes status — from the board dropdown, drag-and-drop, or an automatic close — Woes moves the Jira issue to the matching status (see the mapping below). Sync is best-effort: a Jira hiccup never blocks the support workflow. * **Status sync (Jira → Woes).** A change to the linked Jira issue flows back into Woes. When the ticket moves to a new workflow category (To Do / In Progress / Done), Woes updates the linked support issue's status to match. * **Create Jira issues from automations.** Add **Create Jira issue** as a "then" action in an automation. When the automation fires, Woes creates (and links) a Jira issue for the conversation in your default project. It runs once per conversation — an already-linked issue is never duplicated. * **Disconnect** at any time from the Jira card when Woes should stop using the Jira site. ## Where it appears in Woes * **Workspace Settings → Integrations** — connect, disconnect, and set the default Jira project. * **Issue detail drawer** — a Jira panel with **Create Jira issue** (or **View in Jira** once linked). * **Automations** — **Create Jira issue** is available as a "then" action when building an automation. ## Status mapping **Woes → Jira** (when a support issue's status changes): | Woes issue status | Jira transition | | -------------------- | --------------- | | Closed / resolved | Done | | On you / on customer | In Progress | | New / on hold | To Do | Woes transitions to the nearest matching workflow transition available on the Jira issue. **Jira → Woes** (when the linked Jira issue changes). Woes reads Jira's status *category* (not the display name), so it works across custom workflows: | Jira status category | Woes issue status | | -------------------- | ----------------- | | Done | Closed | | In Progress | On you | | To Do | New | ## Setup 1. In Woes, open **Workspace Settings -> Integrations**. 2. Select **Jira** and click **Connect**. 3. Authorize the Jira Cloud site you want Woes to use. 4. Return to Woes and choose the default Jira project for newly created issues. 5. Open a Woes support issue and use **Create Jira issue** to test the link. If the Jira card says **Setup needed**, contact your Woes workspace admin or Woes support. ## Data And Access Woes keeps the Jira connection server-side and shows only safe site, project, issue key, URL, and status information in the workspace UI. Woes does not show Atlassian personal data such as account IDs, names, emails, avatars, reporters, assignees, or commenter identities in customer-facing views. Inbound sync uses the Jira issue key and status category to keep linked Woes issues aligned. ## Current limits * **Status, not content.** Sync in both directions covers issue status only. Comments, attachments, and field edits are not mirrored. * **No Atlassian user data.** By design, Woes stores no Atlassian account identities (reporter, assignee, commenter). Inbound sync is status-only and never records who made the change. ## Good first use cases * Escalate a reproducible bug from a support issue into your engineering backlog without retyping context. * Keep the Jira ticket's status honest by driving it from the support issue's lifecycle. * Give operators a one-click jump from the support issue to the engineering ticket that owns the fix. ## Related docs * [Integrations Catalog](/integrations-catalog/overview) * [Issues](/support-workflows/omnichannel-support) * [Settings overview](/settings/overview)