> ## Documentation Index > Fetch the complete documentation index at: https://docs.incident.io/llms.txt > Use this file to discover all available pages before exploring further. # Syncing follow-ups with your issue tracker > Track follow-ups in the tool your engineers already work in, without anyone updating two systems. Nobody wants to work their follow-ups in two places. Export a [follow-up](/post-incident/follow-ups) to your issue tracker and it becomes an issue in the project your team already plans from. We then keep reading that issue and updating the follow-up, so closing the ticket in Jira closes the follow-up here. ## Supported issue trackers Connect a tracker from [Settings → Integrations](https://app.incident.io/~/settings/integrations), then export follow-ups to it from the dashboard, from Slack, or automatically. | Tracker | What we create | | ------------------------------------------ | ---------------------- | | [Asana](/integrations/asana) | Task | | [Azure DevOps](/integrations/azure-devops) | Work item | | [ClickUp](/integrations/clickup) | Task | | [Freshservice](/integrations/freshservice) | Ticket | | [GitHub](/integrations/github) | Issue | | [GitLab](/integrations/gitlab) | Issue | | [Jira Cloud](/integrations/jira) | Issue | | [Jira Server](/integrations/jira-server) | Issue | | [Linear](/integrations/linear) | Issue or project | | [Notion](/integrations/notion-follow-ups) | Database page | | [ServiceNow](/integrations/servicenow) | Task or problem record | | [Shortcut](/integrations/shortcut) | Story | * **GitHub and Notion are opt-in.** Turn on **Use as issue tracker** on the integration in [Settings → Integrations](https://app.incident.io/~/settings/integrations) before they appear as export targets. A Notion database also needs a **Status** property, and the [Notion follow-ups](/integrations/notion-follow-ups) page covers the column conventions. * **ServiceNow lets you choose the record type.** Set **Create as** to either a task or a problem record. * **Linear can create a project instead of an issue.** Set **Create as** to `Project` on the export template. See [Linear](/integrations/linear) for what a project supports. Priority sync is off until you enable it. See [follow-up priorities](/post-incident/follow-up-priorities). ## What syncs We create the issue from your export template, add a footer reading `This ticket was created from , using incident.io`, and link the two records together. After that, changes are made in your issue tracker, and we keep the follow-up in sync. | Field | Notes | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | Title | Renaming the issue renames the follow-up. | | Description | Editing the issue's description updates the follow-up. | | Status | Completing the issue completes the follow-up. Jira Cloud, Linear, Notion and ServiceNow also read a canceled or won't-do state as **Not doing**. | | Completion date | Taken from the issue's own resolution or completion timestamp. | | Owner | Only where the tracker reports an assignee we can match to an incident.io user who has access to the incident. See [Owner sync](#owner-sync). | | Labels | Synced from Asana, Azure DevOps, ClickUp, GitHub, GitLab, Jira Cloud, Jira Server and Linear. | | Priority | Only with priority sync enabled, and only where the priority names match. With it disabled, priority is yours to set in incident.io. | | Assigned team | An incident.io concept, so it stays yours to set at any time. | ### Owner sync We match the issue's assignee to an incident.io user and make them the follow-up owner, as long as they can access the incident. On a private incident, an assignee who isn't a participant leaves the follow-up unowned rather than being pulled in. A Notion database with no **Assignee** or **Owner** people column keeps whichever owner you set here. ### Linking to the incident's own ticket If the incident also has its own ticket in the same tracker, we tie the follow-up to it: * **Jira Cloud** links the follow-up issue to the incident ticket as its parent, when both sit in the same Jira site and you leave **Connect to parent issue** on. * **Linear** moves the follow-up into the incident's Linear project, where the incident's ticket is a project. ## Exporting automatically Rather than exporting each follow-up by hand, route them automatically with **export templates** and conditions from [Settings → Follow-ups](https://app.incident.io/~/settings/follow-ups). [Auto-exporting follow-ups](/integrations/auto-export-follow-ups) walks through the setup. ## Attaching issues that reference an incident Mention an incident reference like `INC-123` in a Jira Cloud ticket's title or description and we attach that ticket to the incident as a follow-up. Paste an issue link into the incident's Slack channel and we do the same, for Asana, ClickUp, Freshservice, GitHub, GitLab, Jira Cloud, Linear, Notion and Shortcut. Links in a Google Docs or Confluence post-mortem are picked up too, which you can turn off from [Settings → Post-mortem](https://app.incident.io/~/settings/post-mortem) with **Automatically sync follow-ups from post-mortems**. Whenever we attach one, we post a message in the incident channel with an **Undo** button, and we only attach issues that are still open. You can always do it yourself instead. Export a follow-up and choose **Connect to existing**, or create a follow-up from the **Import** tab by pasting the issue URL. Linking by hand takes the title, description, status and owner from the issue, and works on closed issues too. ## Disconnecting a follow-up To manage a follow-up in incident.io again, disconnect it from its issue. Every field becomes editable here, and we stop syncing. A follow-up carries one issue at a time, so to point it at a different one, disconnect first and then connect the new one. ## Working with the API The [follow-ups API](/post-incident/follow-ups-api) reads and writes follow-ups: list, show, create, update and delete, plus an action to connect a follow-up to an existing issue by URL. ## FAQs It's exported, so the issue in your tracker is where those fields live. Edit it there and the follow-up updates to match. We look for the reference in the ticket's title or description, and we aren't mind readers yet, so a mention in a comment won't do it. We also leave closed tickets alone. Link it yourself instead: export the follow-up and choose **Connect to existing**, which works on closed tickets too.