--- title: "Connect a project to Jira" description: "Hand each new task of a project over to Jira as an issue: the Atlassian consent, choosing the site, project and issue type, the assignee and due date" category: integrations section: native-integrations type: Tutorial lastUpdated: 2026-09-30 locale: en canonical: https://support.talkspirit.com/en/integrations/connect-a-project-to-jira --- # Connect a project to Jira > **In summary:** open the project’s settings, then the **Integrations** tab, and select **Connect** on the **Jira** card. Atlassian asks for your consent on its own screen. Back on the project, choose a **Site**, a **Project** and an **Issue type**, then **Confirm destination**. Each new task becomes a Jira issue, with one assignee and its due date. This guide covers Jira. How the hand-off works, which tasks are sent and why a project holds one project tool at a time is the same for every tool: see [Connect a project to a project tool](/integrations/connect-a-project-to-a-project-tool). ## Before you start - You are an **owner or editor** of the project in Talkspirit. - You have an Atlassian account that can create issues in the Jira project you want. Every issue is created with this account. - The project is not connected to another project tool. If it is, disconnect that one first. ## Connect the project 1. Open the project’s settings, then the **Integrations** tab. 2. On the **Jira** card, select **Connect**. 3. Atlassian shows its consent screen. Sign in if asked, and allow Talkspirit to read users and work items and to create them. The consent includes offline access, so issues are created while you are away. 4. You return to the project. The card reads **Choose a destination**. 5. Choose the **Site**, then the **Project**, then the **Issue type**, and select **Confirm destination**. The card reads **Connected** and names the destination as *Site → Project → Issue type*. ## The destination | Level | What you choose | | --- | --- | | **Site** | One of the Atlassian sites your account can reach. If you have several, you choose, rather than getting the first one. | | **Project** | A Jira project of that site. | | **Issue type** | The type every new issue gets, for example Task or Story. | To send tasks to another Jira project or issue type, select **Change destination**. No new consent is needed. ## What an issue carries | Issue field | Filled with | | --- | --- | | Summary | The task's title | | Description | The task's description, with bold, italic, code, links, headings and lists kept. Checklists, tables and quotes keep their text without their layout | | Assignee | One person, see below | | Reporter | The task's creator, when possible, see below | | Due date | The task's due date, when it has one | The issue does not link back to the Talkspirit task. Once Jira confirms the issue, the task is marked done in Talkspirit and shows an **Open in Jira** link to the issue. ## The assignee and the due date A Jira issue has one assignee, and a Talkspirit task can have several. Talkspirit looks the assignees up by **email address**, in the task's order, and keeps a match only when Jira returns the same address. The **first** confirmed person is assigned. The others are not. A role or a circle assigned to the task is not sent: it has no email address. The due date is the day the task's creator picked, in their own time zone. If Talkspirit does not know that time zone, the day is taken in UTC. If Jira refuses the assignee or the due date, the issue is still created without it. ## The reporter The person who created the task in Talkspirit becomes the issue's reporter. Talkspirit looks them up by **email address**, like an assignee. Two conditions apply: - The **Reporter** field is on the create screen of the chosen Jira project and issue type, and the account that connected Jira is allowed to set it. - The creator's email address matches a Jira account. When either is missing, the issue is created anyway, and Jira records the account that connected Jira as the reporter. ## When issues are not created When sending stops, the card on the project reads **Interrupted** and an alert says why and what to do: see [Connect a project to a project tool](/integrations/connect-a-project-to-a-project-tool). | What you see | Likely cause | What to do | | --- | --- | --- | | The card reads **Interrupted**: *Access to Jira was withdrawn.* | The consent was withdrawn | **Disconnect** Jira and connect it again | | The card reads **Interrupted**: *5 deliveries failed in a row.*, and the connection is recent | The issue type requires a field Talkspirit does not fill, for example an epic name | **Change destination** and choose another issue type | | The card reads **Interrupted**: *5 deliveries failed in a row.* | Jira refused five issues in a row, for example because your account lost access to the site or the Jira project | **Change destination** and choose it again, or disconnect Jira and connect it again | | One task was not marked done, the next ones were | Jira refused that one request, for example because it was busy | Create that issue by hand | | An issue arrived without an assignee | No assignee's email address matches a Jira account, or Jira refused the assignee | Assign it in Jira | | **Connect** cannot be selected | Another project tool is connected to the project | Its tooltip names it: disconnect it first | Tasks created while sending was interrupted are not sent later. ## What’s next? - [Connect a project to a project tool](/integrations/connect-a-project-to-a-project-tool): the hand-off, which tasks are sent, and one tool per project. - [Connect a project to Trello](/integrations/connect-a-project-to-trello) - [Connect a project to Asana](/integrations/connect-a-project-to-asana) - [Connect a project to Basecamp](/integrations/connect-a-project-to-basecamp)