Analytics and advertising cookies

Google Analytics, Vercel Web Analytics, Leadsy and the TikTok Pixel stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.

Skip to content
StellarFirmStellarFirm
Book a demoJoin the waitlist
Mission manual
Esc

Type a word to search every page. Try , or .

Module 06 · Integrations

Jira and Confluence

Coming soon

Let your assistants read Jira issues and Confluence pages while they plan and build. Read only, through Atlassian's own hosted connector. Coming soon.

View as Markdown
On this page

Jira holds your tickets and Confluence holds your team's documents. Once you connect them, your assistants can read an issue or a page before they start, so the work follows what your team already wrote down.

Which assistants use it#

AssistantStatus
CoderAvailable
Product ownerComing soon
SupportComing soon

The Coder is the only persona available today. The Product owner and Support are Coming soon.

What assistants can do#

Jira and Confluence connect through Atlassian's own hosted connector, and they are read only.

AbilityHow it runs
Read Jira issuesReads on its own
Read Confluence pagesReads on its own
Anything that would create or change an issue or a pageNever run from chat

Setup (when it opens)#

  1. Ask an administrator of your Atlassian organization to allow token sign-in for the hosted connector. Without that, Atlassian refuses the connection.
  2. Create a token. Either make a personal token in your Atlassian account (you will also enter your account email), or ask your administrator for a service-account token (no email needed).
  3. Open Integrations in StellarFirm and pick Jira and Confluence.
  4. Paste the token, add your account email if you used a personal token, switch on the live option, and press Connect.

Permissions#

  • The assistants see what the token's owner can see. A service account that can read only one project keeps the assistants to that project.
  • Nothing here waits for an Approve because nothing here changes data. Creating or editing issues and pages is never run from chat.
  • Revoke the token in Atlassian whenever you want to cut access.

Good to know#

  • A personal token is quick to try, but a service-account token is the better long-term choice: it does not depend on one person's account.
  • During a coding session the Coder gets read-only tools for the connected tools. A personal token with an email is used for chat reads only, so use a service-account token if you want coding sessions to see Jira and Confluence too.
  • Give the issue key (for example PROJ-123) in your message. It is the fastest way to point at the right ticket.

Prompts to try#

PromptWork the top ticket
Coder, find the highest-priority open Jira issue in [project], implement it, and wait for my Approve before you push.
PromptRead a ticket first
Read Jira issue [issue key] and tell me what is being asked and what is still unclear. Read only.
PromptCheck the docs
Coder, find the Confluence page about [topic] and tell me whether our code still follows it.