Connect Jira | Docs | Fivo University

Jira is often the system of record for what the team committed to build. Connected to Fivo, its issues feed your graph, meeting action items become tickets, and ticket changes flow back as they happen.

What it adds to your Brain

For each project you choose, Fivo reads its issues: summary, description, status, assignee, reporter, priority, due date, labels and issue type, plus the comments on each issue with their authors. An issue and its comments form one episode.

Fivo also writes. Action items detected in a meeting can be created as Jira issues of type Task in the project you chose, assigned to the matching Jira user when the name matches. When an issue Fivo created changes status or due date, is commented or deleted in Jira, the task in Fivo updates. You can turn on instant task delivery so tickets are created as soon as a meeting ends, for your own meetings or for meetings you are invited to. Jira does not receive meeting reports, only tasks. See Tasks and commitments.

Example question your AI can then answer: "What is blocking the Atlas rollout, and which standup discussed it?"

Before you start

An Atlassian account with access to the Jira site and projects you need.
Grant every permission Jira asks for. Fivo checks the grant and refuses a narrowed one, because without the webhook permission it cannot receive changes.
Organization scope requires the organization owner. See Connect your tools.

Step by step

Open Integrations in app.fivo.ai and find Jira.
Click Connect. Atlassian opens its authorization page. You approve permissions to read Jira users and work, create and edit work, manage webhooks, and stay connected without signing in again.
Back in Fivo, the site you granted is adopted automatically. In the integration's Configuration, choose:
- Site: your Jira site, if you reach more than one.
- Project: the project where tasks will be created (for example DEV or MKT).
- Instant task delivery for your meetings and for meetings you are invited to, if you want tickets created automatically.
Save.
To feed your graph, go to the Brain view, connect Jira as a source and pick the projects to read. Fivo lists every project of every site you reach, named after its site.

What happens next

Fivo reads each project's issues updated within the history window of the source, newest first, with their comments. It registers one webhook per Jira site, so new and updated issues and new comments reach your graph as they happen, and the issues Fivo created sync their status back immediately. Jira webhooks expire and Fivo renews them. Projects are also re-read on a regular schedule.

Jira tells Fivo who can browse a project, so with organization scope a project's facts are visible to the people with that permission in Jira. See Permissions: what your Brain can see.

Disconnect

Open Integrations, select Jira and click Disconnect. Fivo removes the webhooks it registered. To stop reading one project while keeping sharing, use Remove from graph in the Brain view.

Troubleshooting

"Jira permission missing." Jira connected, but the webhook permission was not granted, so Fivo could not register the webhook. Reconnect and approve every permission.
"Jira webhook not registered." Jira rejected the registration. Live updates may be delayed; Fivo keeps reading on its schedule. Try reconnecting later.
"Your Jira connection is no longer valid." The grant expired or was revoked. Reconnect to restore it.
Tickets arrive unassigned. Fivo matches the assignee's name against the users assignable in the project. A name that does not match closely enough leaves the ticket unassigned.
The project list is empty. Jira limits how fast projects can be listed. Wait a moment and open the configuration again.

integration
tasks