Atlassian

The Atlassian integration connects Jira and Confluence to Sprigr Teams. Agents can search and read Jira issues, create and update tickets, add comments, log work, manage sprints, and read and write Confluence pages. It is useful for teams that track work in Jira and keep documentation in Confluence.

Note

Atlassian ships as a first-party marketplace app, not a built-in Integration Hub connector. You install it from the Apps section rather than the Integrations page. It is a per-user connection: each person connects their own Atlassian account, and the app is private to that person’s agent by default.

Prerequisites

• An Atlassian Cloud account with access to the Jira and Confluence sites you want to use.
• Admin or Owner role in your Sprigr Teams organisation to install the app.
• Each user who wants to use it connects their own Atlassian account, so actions run with that user’s permissions.

Installing Atlassian

1. Open the Apps section

   Sign in to team.sprigr.com and open the Apps section from the sidebar.

2. Find Atlassian

   Locate the Atlassian app and install it.

3. Authorise with Atlassian

   Connecting runs an OAuth flow at auth.atlassian.com. Sign in, choose the Atlassian site you want to use, and review the requested permissions. The app requests read and write access to Jira work, read of Jira users, Jira webhook management, read and write of Confluence content, Confluence search, and offline access for token refresh.

   Click Accept to grant access. During the callback, Sprigr records the Cloud ID and site name of the site you selected so the tools know which site to call.

4. Verify the connection

   Once connected, the Atlassian app appears in your installed apps and its Jira and Confluence tools become available to your agent.

Tip

Atlassian data is treated as confidential to the connected user. The app will not share Jira issue details or Confluence page content with other users or agents unless you explicitly ask it to, and it cites Jira issues by their issue key (for example PROJ-123).

Try asking your agent

“Find all my open Jira issues in the PLATFORM project ordered by most recently updated, and summarise what’s in progress.”

“Create a bug in PROJ titled ‘Checkout fails on Safari’ and set the priority to High.”

Available tools

When your agent has the Atlassian app connected, it gains access to the following tools.

Jira

Tool	Description
jira_search	Search Jira issues using JQL (Jira Query Language)
jira_get_issue	Get full details of an issue by key, including description, comments, and worklogs
jira_create_issue	Create a new issue (requires a project key, issue type, and summary)
jira_update_issue	Update fields on an existing issue
jira_transition_issue	Move an issue to a new status, or list available transitions
jira_add_comment	Add a comment to an issue
jira_log_work	Log time spent on an issue
jira_link_issues	Create a link between two issues (for example “blocks” or “relates to”)
jira_get_board	Get a board with its active and future sprints and sprint issues
jira_list_projects	List the Jira projects the user has access to

Confluence

Tool	Description
confluence_search	Search Confluence pages using CQL (Confluence Query Language)
confluence_get_page	Get the full content of a page by ID
confluence_create_page	Create a new page in a space
confluence_update_page	Update an existing page
confluence_list_spaces	List the Confluence spaces the user has access to

Note

Jira descriptions and comments are written in plain text and converted to Atlassian Document Format automatically. Confluence page bodies use Confluence storage format (an HTML-like markup); plain text is also accepted.

Common use cases

• Issue triage — An agent searches Jira with a JQL query, summarises what is open, and flags anything unassigned or overdue.
• Ticket creation from chat — A team member describes a bug in conversation and the agent creates a Jira issue with the right project, type, and priority.
• Status updates — The agent transitions an issue from “In Progress” to “Done” and logs the time spent.
• Sprint review — The agent pulls a board’s active sprint and lists its issues by status and assignee.
• Documentation lookup — The agent searches Confluence for a runbook or policy page and returns the relevant content.
• Writing back to Confluence — The agent drafts meeting notes or a summary and creates or updates a Confluence page in the right space.

Troubleshooting

“cloudId not configured” errors The tools need the Cloud ID that is captured during the OAuth callback. If you see this error, reconnect the Atlassian app so the Cloud ID and site name are recorded again.

“Unauthorised” or token errors Atlassian uses rotating refresh tokens. Sprigr Teams refreshes and persists them automatically. If errors persist, reconnect the app from the Apps section.

Agent cannot see an issue or page The connection is scoped to the connected user’s Atlassian permissions. If an agent cannot find an issue or page, confirm the connected account has access to it.

Wrong site The app calls the Atlassian site you selected during OAuth. If you have multiple sites, reconnect and choose the correct one.

Next steps

• Integrations Overview — See all available integrations.
• Creating Agents — Give an agent a persona tailored to project management queries.
• Workflows — Use Jira and Confluence actions as steps in automated workflows.