Skip to main content

Jira

The Jira integration is two-way, which makes it different from Kinn's other sources. Kinn doesn't just read your existing issues — it can also create new ones and update existing ones in the projects you connect. That's what closes the loop between a problem surfacing in your community and a tracked ticket in your backlog.

Jira support is for Jira Cloud (Atlassian-hosted). Self-hosted Jira Server / Data Center isn't supported.

caution

Unlike Discord, Reddit, and YouTube — which only read public content — Kinn can make changes in Jira: it can create and update issues in the projects you connect. Connect only the projects you're comfortable having Kinn write to.

What it pulls in​

For each project you connect, Kinn reads the issues and their details:

  • Issue summary, description, and comments
  • Status, labels, issue type, and priority
  • Ongoing changes as issues are updated

Kinn only reads from the projects you explicitly select — projects you don't connect are never touched.

Creating and updating issues​

Because the integration is two-way, Kinn can also write to your connected projects:

  • Create issues — turn a bug Kinn detected across your community sources into a tracked ticket, without re-typing it by hand.
  • Update issues — add context to an existing ticket or adjust it as part of triage.

Kinn does not delete issues. Writes are limited to the projects you've connected.

See Bug detection & triage for how detected problems become tickets.

How to connect​

You'll authorize Kinn against your Atlassian account, so you'll need permission to grant access to the Jira Cloud site and projects you want to connect.

  1. From your dashboard, go to Sources → Add source → Jira.
  2. Authorize Kinn through your Atlassian account when prompted. The consent screen will show exactly what access Kinn is requesting (see Permissions).
  3. If your account has more than one Jira Cloud site, choose the site, then select the specific projects you want to connect.
  4. Wait for the initial sync to finish. Once it shows as synced, Kinn can read those projects and is ready to create or update issues in them.
tip

Start by connecting a single project — likely whichever one your bug reports already land in — so you can see how Kinn reads and writes before you widen access to more of your backlog.

Permissions​

Kinn requests both read and write access, scoped to the projects you select:

  • Read access to issues, comments, and issue metadata — to ingest your backlog.
  • Write access to create and update issues — to push detected bugs and triage updates back into Jira.

The exact scopes appear on the Atlassian consent screen when you authorize. Access is limited to the Jira Cloud site and projects you connect; Kinn does not delete issues and does not touch projects you haven't connected.

What you can now ask and do​

Once Jira is connected and synced, you can ask questions like:

  • Which reported bugs from the community aren't tracked in Jira yet?
  • Do any of this week's complaints match existing open tickets?
  • What are the most-mentioned problems that don't have a ticket?

And, because the integration writes back, you can act on what you find — for example, creating a Jira issue directly from a bug Kinn surfaced across your sources, rather than copying it over manually.

See Writing good queries for sharper questions, and Example queries for a fuller library.