Send a Task to Jira

min read - Updated on Oct 28, 2026

You can send a Kimola Task to Jira as a new issue, or link it to an issue your team already has, so the work is planned and done in Jira while Kimola keeps the finding behind it. You do it from the JIRA card on the Task's page: pick a project and an issue type to create a new issue, or type the key of an existing one, such as CX-123. From then on, the Task's status, assignee and due date follow the issue, and once the work is done, Kimola still measures whether customers noticed.

Getting Ready

Tasks and the Jira integration are available in the Enterprise package. They are also available in Kimola On-Premises.

Jira must be connected for your team. See Connect Jira to Kimola.

A Task carries a finding and the feedback behind it to the teammate who can act on it. Kimola isn't a task tracker: the work itself happens in your team's tool, and the loop closes back in Kimola. Sending a Task to Jira puts the work where your team already plans it, with the evidence attached, so whoever picks up the issue knows why it matters.

Send a Task as a New Issue

Send a Task as a new issue when the work isn't in Jira yet. Kimola creates the issue in the project you pick, with the finding and its feedback, and keeps the Task with that issue.

To open a Task, go to TASKS in the main menu and click View on the Task. The JIRA card is on the Task's page. If Jira isn't connected for your team, the card says Connect Jira to send this task there and follow it from here; the connection is described in Connect Jira to Kimola.

On the JIRA card, choose the project and the Issue type the Task becomes, such as Task or Story. Your team's default project and issue type are used unless you pick others. The issue types come from the project, so the list says Pick a project first until a project is chosen. Then click Send to Jira.

The new issue carries the finding, its numbers and a few pieces of feedback in customers' own words. Emails and numbers in the feedback are masked, so customers' personal details don't leave Kimola in the issue's text. The Task's priority, assignee and due date go with it; if the Jira project doesn't accept one of them, the issue is created without it.

Note

Emails and numbers in the feedback are masked in the issue.

Example

For a mobile network operator, a Task made from the theme coverage in rural areas goes to the network team's Jira project as a Task issue. The engineer who opens the issue reads how much of the feedback mentions the theme, how negative it is, and a few survey answers from customers in small towns, without signing in to Kimola.

You can also send a Task to Jira as you make it. If your team has a default project, the window where you make a Task offers Also send to Jira, which sends the new Task as an issue as soon as it is created. See Create a Task.

Tip

Choose Also send to Jira while you make a Task to send it without opening its page.

Link an issue when the work is already in Jira, for example when your team opened an issue about the same problem before the finding showed up in Kimola. Linking keeps the Task with that issue instead of creating a second one.

On the JIRA card, click Link an issue and type the issue's key in the field that says Issue key, e.g. CX-123. Kimola reads the issue and links it to the Task.

Once the issue is linked, the Task takes its status, assignee and due date from the issue, as a sent Task does. The Task keeps its evidence in Kimola, and Kimola measures the same feedback once the work is done, whichever way the Task reached Jira.

Note

A linked Task takes the issue's status, assignee and due date in place of its own.

What Follows Jira

Once a Task is sent to Jira or linked to an issue, the JIRA card says "Its status, assignee and due date follow the issue." Your team updates the work in Jira, and Kimola keeps the Task up to date as the issue changes.

Status: an issue in Jira's to-do statuses keeps the Task Open, an issue in progress makes it In progress, and a done issue makes it Done. An issue resolved as won't do makes the Task Won't do. The Task's status can't be changed in Kimola while it follows the issue.

Assignee: the teammate whose email matches the issue's assignee in Jira. The match works when your teammates use the same email address in Jira and in Kimola.

Due date: the issue's due date.

Tip

Use the same email address in Jira and in Kimola, so that an issue's assignee is matched to the right teammate.

A Task that is done in Jira is done in Kimola too, so its measurement starts on its own. Two and four weeks after the Task is done, Kimola reads the same feedback again and shows under DID CUSTOMERS NOTICE? whether customers noticed. It writes the four-week result to the Jira issue as well, and so does a later check that finds the problem came back. See How Kimola Measures Task Impact.

Comments on a Task become read-only once it is in Jira, because the conversation moves to the issue. The changes that come from Jira, such as a new status or assignee, are listed in the Task's HISTORY and marked as Jira's. See Follow a Task.

Note

The Task's status follows the issue and can't be changed in Kimola.

If your team's Jira connection expires, the Task stops following its issue until the connection is renewed, and the JIRA card says "The Jira connection expired." with Connect it again. The Task keeps its issue meanwhile, so once Jira is connected again, it follows the issue again without being sent a second time. See Connect Jira to Kimola.

Unlink a Task when it was sent to the wrong project or linked to the wrong issue, or when your team no longer wants to follow the work in Jira. On the JIRA card, click Unlink.

Unlinking separates the Task from the issue. The Task stays in Kimola with its evidence, comments and history, and the issue stays in Jira. The Task no longer follows the issue, so its status, assignee and due date are changed in Kimola again, and you can send it to Jira or link it to another issue.

Note

Unlinking doesn't delete the issue in Jira.

Was this article helpful?

Tell us about your thoughts and experiences regarding the article.