Jira
Tickets, their descriptions and comments become memory. Changes arrive by webhook.
Status: Available. One Atlassian connection covers Jira and Confluence.
What SeamTrail reads
- The tickets linked to a feature, and the tickets under a linked epic.
- Each ticket's title, status, owner, parent, team and blockers.
- Descriptions and comments. They become memory of that ticket. A decision in a comment can start a drift check.
- Links between tickets, like "is blocked by".
How changes arrive
- Webhook. SeamTrail registers its webhook in Jira when you connect. It keeps it renewed.
- A check every 6 hours fills any gap, in case a change was missed.
Permissions
| Permission | Why SeamTrail asks for it |
|---|---|
read:jira-work | Read tickets, comments and links. |
write:jira-work | Make the changes you confirm: create tickets from the Plan, and move, comment on or assign a ticket from the chat. |
read:jira-user | Show who owns a ticket. |
manage:jira-webhook | Register the webhook that tells SeamTrail about changes. Only the org's connection asks for this. |
offline_access | Stay connected without asking you to sign in again. |
Connect
- Open your org's Settings → Tools.
- Next to Jira + Confluence, click Connect. (Org Admins and Managers.)
- Pick your Atlassian site and accept.
Then each person adds their own login: your own Settings → Connections → Connect your login. Pick the same site your org uses.
Good to know
- SeamTrail never writes into Jira on its own. It changes a ticket only when you confirm it in the chat or the Plan.
- A ticket counts as done when its status is in Jira's Done category. So your own "Shipped" status counts too, if it is in that category.
- When a ticket is done, the open blockers, risks and questions about it close by themselves.
- SeamTrail keeps the Atlassian account ID next to each name it stores. When Atlassian says an account was closed, SeamTrail replaces the name with "Former user". See Privacy.