Connecting Jira to KlaritiQ

If your team already tracks work in Jira Cloud, you can connect it to KlaritiQ so that the tasks and risks on an initiative and the issues in a Jira project stay in step. Change something in one place and it shows up in the other. Nobody has to copy anything across by hand.

The two protections that make KlaritiQ different still apply. A task that needs evidence is not completed because someone dragged its Jira issue to Done, and a risk is not resolved from Jira. Both wait for a person in KlaritiQ.

Before you start

• You need to be an owner or admin of your KlaritiQ organization.
• Your Jira has to be Jira Cloud. Jira Server and Data Center are not supported.
• The Atlassian account you connect with must be able to see the Jira project you want to link.
• People are matched by email address. Someone whose email Jira does not show, or who is not a KlaritiQ member, is simply left alone.

Step 1: Open Integrations

Go to Integrations in the admin menu. Under Workspace connections find Jira. Every connection is a short row, so choose Show details to open it. It opens by itself when it needs your attention.

If the card says Not enabled, Jira has not been switched on for your KlaritiQ workspace yet. Contact support and we will switch it on.

Step 2: Connect Jira

Choose Connect Jira. You are taken to Atlassian's own screen. Pick the Jira site you want, then approve. Atlassian words the permissions in its own way, but they come down to four things:

• view and change Jira issues, which is how tasks and risks are created and updated
• view Jira user profiles, which is how people are matched by email
• manage Jira's change notifications, so updates arrive quickly
• stay connected without asking you to sign in again

You are brought back to KlaritiQ, where the card shows Connected and the name of your Jira site. If your Atlassian account has more than one Jira site, you can choose between them here until the first initiative is linked.

Step 3: Link an initiative to a Jira project

Linking is done one initiative at a time, from the Jira card on the Integrations page. Under Initiatives, choose Manage next to the initiative you want.

1. Choose the Project you want.
2. Choose the issue type new issues should have, such as Task.
3. Choose what to sync: Tasks, Risks, and whether to bring in Jira issues labelled klaritiq as tasks.
4. Choose Link to Jira.

The first sync starts straight away. There is nothing to map by hand: statuses are matched through Jira's three fixed categories, To Do, In Progress and Done, whatever your workflow calls them.

What gets synced

• A task or risk in KlaritiQ becomes a Jira issue labelled klaritiq (risks also get klaritiq-risk), with a link back to KlaritiQ.
• A Jira issue in the linked project that you label klaritiq becomes a KlaritiQ task.
• The title, due date (tasks), priority (a risk's severity), assignee and status are kept in step in both directions. If both sides changed the same field, the more recent change wins.
• The description is copied once, when the issue or task is first created.
• Work that is already finished is not sent to Jira when you link an initiative.

Each issue KlaritiQ creates ends with a KlaritiQ ID line in its description. That is how KlaritiQ recognises its own issues again after a disconnect or a project change, so please leave that line in place.

When Jira says Done

• A task with required evidence is not completed. It stays open in KlaritiQ and the Jira issue gets one comment explaining why. It completes by itself once the evidence is verified.
• A task without required evidence is completed.
• A risk is never resolved from Jira. It shows as waiting under that initiative on the Jira card, and an owner or admin chooses Approve resolution, which records the decision as it always does.
• If an issue is moved back out of Done in Jira, the task or risk is reopened in KlaritiQ.

How quickly changes arrive

Jira tells KlaritiQ when something changes, so updates usually arrive within a few minutes. A full check also runs every hour, and an admin can choose Sync now at any time.

Changing or stopping the sync

• Unlink an initiative from its settings on the Jira card to stop syncing it. Nothing is deleted in Jira or in KlaritiQ. Linking the same project again picks up the existing issues instead of creating them twice.
• Disconnect Jira from the Jira card to stop syncing everywhere. Again nothing is deleted on either side. To withdraw Atlassian's access completely, also remove KlaritiQ from the connected apps in your Atlassian account.
• Neither side ever deletes the other's records. If an issue is deleted in Jira, or an item is removed in KlaritiQ, the link is dropped and the other side is left as it was.

If something looks wrong

• Reconnect needed: Atlassian access was withdrawn or has expired. An admin chooses Reconnect on the Jira card.
• Will retry next to an item: Jira refused a change, for example because your workflow does not allow that move or a field is required. Fix it in Jira and the next sync carries on.
• Assigned in Jira to someone who is not a KlaritiQ member: the owner in KlaritiQ is left as it was, and the Jira assignee is not changed.
• If two organizations on the same Jira site link the same project, a Jira issue belongs to the first organization to link it.

For what each connection can access and how credentials are protected, see How KlaritiQ Integrations Work. For how evidence gates a task, see Understanding Evidence.

Was this article helpful?

Community Questions (0)

Still have questions?