Connect Jira to Kimola

min read - Updated on Oct 28, 2026

You can connect Jira Cloud to Kimola so that your team's Tasks go to Jira as issues and their progress comes back to Kimola. You connect once for the whole team: you allow Kimola in Atlassian's window, then choose the Jira site, the default project and the default issue type that tasks are sent to. From then on, anyone in your team can send a task to Jira as a new issue or link it to an issue that already exists, and the task follows the issue's status, assignee and due date.

Jira is the work management integration of Kimola: the other integrations bring feedback in, and Jira sends work out. See What are Integrations? for the full list.

A Kimola task carries a finding and the feedback behind it to the teammate who can act on it. Connecting Jira lets that work happen in the tool your team already plans with, while Kimola keeps the evidence and later measures whether customers noticed the change.

Getting Ready

The Jira integration is available in the Enterprise package; see kimola.com/pricing. It is also available in Kimola On-Premises, where connecting it is optional and Tasks work the same without it.

Kimola connects to Jira Cloud, the Jira your team opens at an address like https://your-company.atlassian.net. Use an Atlassian account that can see and create issues in the projects your tasks should go to. The connection belongs to your team's Kimola account, so anyone in the team can connect Jira, change where tasks go and send tasks to Jira.

Step 1: Connect Your Jira

You start the connection on the Jira page of your account's integrations. The page explains what a connection does before you connect.

Open ACCOUNT in the main menu and go to Integrations. Under WORK MANAGEMENT ("Where your team's tasks go."), click the Jira card ("Send tasks to Jira and follow their status."). The page that opens is titled Jira, with "Send your team's tasks to Jira and follow them from Kimola." under it.

The Connect your Jira card lists what the connection does. A task goes to Jira as an issue, with its finding, its numbers and a few pieces of feedback, with emails and numbers masked. Its status, assignee and due date come back to Kimola as they change in Jira. An issue you already have can be linked to a task instead.

[Screenshot: The Jira page under Integrations with the Connect your Jira card and the Connect Jira button]

Click Connect Jira. Kimola takes you to Atlassian, which asks you to allow Kimola to read and write issues and to follow their changes. Sign in to Atlassian if it asks you to, choose the Jira site you want to use, and accept. Atlassian then brings you back to the same Jira page in Kimola, now connected.

Kimola asks for these permissions for three reasons. It writes issues when your team sends a task, it reads an issue when your team links one to a task, and it follows the changes of those issues so that each task stays up to date.

Tip

You can also start from a task: if Jira isn't connected yet, the task's JIRA card offers Connect Jira, which leads to the same connection.

Step 2: Choose Where Tasks Go

Once Jira is connected, the same page shows where your team's tasks go. These are defaults: they save time for everyone, and whoever sends a task can still pick another project or issue type for it.

SITE. The Jira site the tasks are sent to.

PROJECT. Under Where tasks go ("The project and the issue type a task is sent to unless whoever sends it picks others."), choose the Jira project that tasks go to by default.

ISSUE TYPE. Choose the issue type, such as Task or Story, that a task becomes in that project. The issue types come from the project you chose, so the list says Pick a project first until a project is selected.

With a default project, the window where you make a task can also send the new task to Jira at once (Also send to Jira). Any task that already exists can be sent from its own page, with Send to Jira, or linked to an existing issue by its key, such as CX-123, with Link an issue. See Send a Task to Jira.

A task sent to Jira becomes an issue with the finding, its numbers and a few pieces of feedback, with emails and numbers masked so that customers' personal details don't leave Kimola in the text. The assignee is matched to a member of your team by email. When Kimola later measures a done task and finds whether customers noticed, it writes the result to the issue as well. See How Kimola Measures Task Impact, and for the whole workflow, How to Close the Loop on Customer Feedback.

Note

Once a task is in Jira, its status, assignee and due date follow the issue, and its status can't be changed in Kimola.

When the Connection Expires

A connection can expire when Atlassian no longer accepts Kimola's access. While it is expired, Kimola can't send tasks to Jira or read the issues of tasks already sent, so those tasks stop following their issues.

The Jira page then shows "The connection expired: Kimola can not send tasks or read their issues until it is connected again." with Connect again. A task's JIRA card shows "The Jira connection expired." with Connect it again.

Click Connect again and allow Kimola in Atlassian's window, as in Step 1. Your tasks keep their issues while the connection is expired, so once it is connected again, they follow their issues again without being sent a second time.

Disconnect Jira

You disconnect Jira on the same Jira page, under Account › Integrations › Jira. Click Disconnect. Kimola shows "Jira is disconnected." and the page offers Connect Jira again.

Disconnecting unlinks every task of your team from its Jira issue. The tasks stay in Kimola with their evidence, comments and history, and the issues stay in Jira. A task no longer follows its issue, so its status, assignee and due date are changed in Kimola again.

Note

If you connect Jira again later, tasks aren't linked back to their old issues by themselves. To keep a task with its issue again, link the issue to the task by its key.

Note

Disconnecting removes the connection from Kimola only. To withdraw Kimola's access completely, also remove Kimola from the connected apps in your Atlassian account.

Was this article helpful?

Tell us about your thoughts and experiences regarding the article.