The Jira integration connects Atlassian Jira projects to 15Five AI. It syncs Jira issues, comments, user references, and work-tracking activity. Agents use this work context alongside 15Five data when generating insights. The integration uses one Atlassian account, and that account’s Jira access defines what syncs.
Access and Availability
| Role | Requirement |
|---|---|
| Atlassian Admin | Required to provision the integration user, add it to Jira projects, and approve OAuth scopes at connect time |
| 15Five Company Admin or IT Admin | Required to initiate the connection from Agents Hub |
Jira Cloud is supported for Jira Software, Jira Work Management, and Jira Service Management.
The same person can hold both roles, or two people can coordinate setup. Jira Cloud only — Jira Software, Jira Work Management, and Jira Service Management are supported. A dedicated integration user is strongly recommended over a personal account; if the connected account is deactivated or loses project access, the integration will break.
Note: To ensure the highest level of security, 15Five is continually investing in our overall information security program, resources, and expertise. To review 15Five's security documents, and how we handle your company data, see our Trust Website.
Feature Structure
The integration is configured from Agents Hub > Integrations > Jira.
Permissions and access
A few things to know about how 15Five AI works with your Jira data:
The connected Atlassian user defines what 15Five AI can see. 15Five AI connects to Jira using a single Atlassian account, the integration user. This means that individual employees do not need to log in. The integration user can access specific projects and issues in Jira, which defines what 15Five AI can see. Any issues that the integration user cannot access will not be visible to 15Five AI.
You set that scope in Jira. You can add or remove the integration user from Jira projects, and the synced scope will change accordingly.
Comment visibility carries through from Jira. Jira allows comments to be limited to specific roles or groups, such as comments that only internal teams can see on a Service Management ticket. This integration records Jira's privacy setting for each comment, so the visibility rules from Jira remain in place.
Read-only. The integration cannot create, edit, transition, or delete any issues, comments, projects, or users in Jira.
What gets synced
Once the integration is set up, 15Five AI syncs issues, comments, and the people linked to them from all accessible Jira projects.
Issues (per synced project):
- Title, description, and type
- Status and priority
- Project, assignees, creator, parent issues, and sub-tasks
- Labels and custom fields — sprint references, story points, custom dropdowns, etc.
Comments:
- Comment body and author
- Privacy status — whether the comment is marked private or restricted in Jira
Users (referenced in synced projects):
- Display name, email, and account status
- Account type — person (
atlassian) or connected app/service account (app)
Not synced: Anything the integration user cannot read in Jira — security-restricted issues, internal-only comments, and projects the user has not been added to.
Backfill and Sync Cadence
On first connect, up to one month of history is backfilled. After that, records sync incrementally multiple times per day. Changes to the integration user's project access are picked up automatically on the next sync cycle.
Permissions Requested
All permissions are read-only — the integration cannot create, edit, transition, or delete any issue, comment, project, or user in Jira.
| Permission | Purpose |
|---|---|
jira-user (View user information) |
Read names, account IDs, avatars, and email addresses of users referenced on issues |
jira-work (Read Jira project and issue data) |
Read issues, comments, projects, statuses, priorities, labels, and associated metadata |
| View application roles | Read Atlassian application role assignments to interpret which users have Jira access |
jira-webhook (Manage Jira webhooks) |
Register webhooks so Jira can notify 15Five AI as activity happens |
Key Rules
- The integration user's project access in Jira is the sole control point for what 15Five AI can see.
- To narrow sync scope, remove the integration user from a project or the group/role that grants access. To broaden it, add the integration user to additional projects.
- Comment visibility from Jira is preserved — private or restricted comments in Jira remain restricted in 15Five AI.
- The integration is read-only; it cannot create, edit, transition, or delete anything in Jira.
- Jira Cloud only — Jira Server and Data Center are not supported.
- A dedicated integration user is strongly recommended. If the connected account is deactivated, the integration will stop working.
- The integration can be disconnected from Agents Hub > Integrations, or by revoking access from the Atlassian side — deactivating the integration user, removing project access, or revoking the app under Atlassian account settings > Connected apps.
Common Questions
What Jira data syncs to 15Five AI?
15Five AI syncs issues, comments, and users from Jira projects the integration user can read. Issue data includes title, description, type, status, priority, assignees, creator, parent issues, sub-tasks, labels, and custom fields. Comment data includes the comment body, author, and privacy status.
What Jira data does not sync to 15Five AI?
15Five AI does not sync Jira data hidden from the integration user. Draft tickets, restricted-project content, attachment contents, security-restricted issues, and internal-only comments hidden from the integration user do not sync.
How is Jira access scoped?
Jira access is scoped through the connected Atlassian account. 15Five AI only syncs projects and issues that account can read. Scope is managed in Jira, not in 15Five.
Why is a dedicated Jira integration user recommended?
A dedicated integration user keeps the connection separate from a personal employee account. It keeps access easier to audit and helps avoid sync interruptions when employees change roles or leave the company.
Can 15Five AI change Jira data?
No. The Jira integration is read-only. 15Five AI cannot create, edit, transition, or delete Jira issues, comments, projects, or users.