Skip to main content
Integration guide

Jira

Compare customer feedback with your backlog and act on issues from Kinn chat.

Connect with
Atlassian authorization
Scope
One Jira Cloud site
Direction
Two-way

Jira connects Kinn chat to your Jira Cloud site. Kinn can search your backlog while answering a question, then create or update an issue when you ask.

Jira Server and Jira Data Center are not supported.

caution

Jira is two-way. Kinn can create issues, add comments, change issue fields and status, and link related issues when you ask. It does not make these changes automatically.

What Kinn can read​

Kinn can search the projects available to the connected Atlassian account and read:

  • Issue summaries, descriptions, comments, and keys
  • Status, issue type, priority, and labels
  • Created and updated dates

For privacy, Kinn removes reporter, assignee, commenter, and mentioned-user identity details before Jira results reach the assistant.

What Kinn can change​

When you ask, Kinn can:

  • Create an issue in a project you name
  • Add a comment to an issue
  • Update its summary, description, labels, priority, or issue type
  • Move it through an available workflow transition
  • Link two related or duplicate issues

Kinn does not delete Jira issues.

How to connect​

You need permission to authorize access to the Jira Cloud site.

  1. Go to Settings → Credentials → Jira and select Connect.
  2. Review and approve the access requested by Atlassian.
  3. If Atlassian returns more than one site, choose the Jira site you want Kinn to use.
  4. Return to chat and ask Kinn to list your Jira projects or search for an issue.

The connection belongs to the Kinn account, so it is available while working with any product in that account.

Permissions​

Kinn requests read and write access to Jira work items, plus permission to keep the connection active. Jira still applies the connected Atlassian user's own project permissions to every action.

To remove access, go to Settings → Credentials → Jira and select Disconnect.

What you can now ask and do​

  • Search Jira for open login bugs updated this month.
  • Does this feedback match an issue already in Jira?
  • Create a bug in the GAME project with links to these reports.
  • Add this customer context to GAME-123.
  • Move GAME-123 to the next available status.
  • Link GAME-125 to GAME-123 as a duplicate.

Kinn shows its tool activity while it works. Check the issue key and project before requesting a change, especially when several projects use similar names.