Better Stack incidents show on the Jira work items they're linked to, so whoever opens a work item sees what's happening and can acknowledge, resolve or reopen the incident without leaving Jira.
You need a Better Stack account, Better Stack's integration for Jira connected on the team whose incidents you want to see, and Jira Cloud. The panel reads the work item links that integration writes, so connect the integration first. Jira Data Center isn't supported.
A Jira site admin installs the app once per Jira site.
The app adds a Better Stack panel to the work item view, a Better Stack page to the Apps menu, and a Better Stack page to Space settings. Nothing shows up in them until the site is connected to a Better Stack team.
This is one connection per Jira site, made once. A Better Stack team member who can manage the team's integrations completes it.
Incidents of that team now show on the work items they're linked to.
Connect the site again from Space settings → Apps → Better Stack to add another team, so one Jira site can serve a support team and a platform team at the same time. Every connected team's incidents show on the work items they're linked to.
You need the permission to manage integrations in that team, and the team needs a Jira integration on this site. A team without one offers Connect Jira instead. It takes you through Jira's authorization, sets the integration up and connects the team on the way back.
Connecting your own account ties your Jira user to your Better Stack user, so your acknowledgements and resolutions are attributed to you. Every responder does it for themselves.
We store your Atlassian account ID and nothing else. No e-mail address, no name, no work item content.
To disconnect it later, go to Settings → Account settings and click Disconnect under Jira account. Your incidents stay where they are, and the action buttons in Jira go away.
The Better Stack panel on a work item lists the incidents linked to it, ongoing first, each with its state, its cause, who acknowledged or resolved it and how long it lasted. The incident name links into Better Stack.
The buttons follow the incident's state:
Every action runs as your own Better Stack account and under your own Better Stack permissions, so nothing can happen from Jira that couldn't happen in Better Stack. The incident timeline names you. Until you connect your account the panel still lists the incidents, with Connect Better Stack account under them instead of the buttons. If you may not act on a team's incidents, the panel says so under the list and names the team.
The panel doesn't poll. It refreshes itself after every action, and again when you come back to the tab.
| What the panel says | What it means |
|---|---|
| Connect this Jira site to a Better Stack team to see and manage incidents here. | The Jira site isn't connected to a Better Stack team yet. Click Connect to Better Stack. |
| Connect your Better Stack account to see the incidents linked to this work item. | The site is connected to teams in more than one Better Stack organization, so the panel confirms who you are before it shows anything. Click Connect Better Stack account. |
| No incidents linked to this work item yet. | Nothing is linked to this work item. See the troubleshooting below. |
| Incidents linked to this work item belong to a Better Stack team that isn't connected to this Jira site yet. | A Better Stack team created or linked this work item but hasn't connected this Jira site. Click Connect to Better Stack and pick that team. |
| Incidents linked to this work item belong to teams you're not a member of. | The incidents on this work item belong to a connected team you can't access. Ask to be added to that team in Better Stack. |
Apps → Better Stack lists the open incidents of the connected teams you can access, ongoing first, with the same states and causes as the panel and links back into Better Stack. On a site connected to several teams, each row names the team it belongs to.
The page is read-only. Acknowledge and Resolve stay on the work item, where Better Stack can check your access to that work item.
To stop a team's incidents from showing in Jira, open Integrations in Better Stack and remove that team's Jira integration. The site connection goes with it, and the other connected teams are untouched.
To remove the app from the Jira site, uninstall it in Jira. Better Stack stops serving the site at once, so the panel and the Apps → Better Stack page disappear. The team connections are kept, so reinstalling the app picks up where it was. Your Jira integration keeps creating and linking work items for new incidents, so uninstall the app only if you want the Jira surfaces gone.
Before it answers, Better Stack asks Jira whether you can open the work item, and this is the answer when Jira says no. Check that you can open the work item and its project in Jira yourself. The same denial reads "Better Stack can't show your open incidents." on Apps → Better Stack.
A temporary problem reaching Better Stack. Click Retry in the message. If it keeps failing, reload the work item.
Only work items Better Stack created or linked for an incident carry one, and that link is written by Better Stack's integration for Jira. A work item created by hand in Jira reads "No incidents linked to this work item yet." So does a work item whose incidents predate the integration.
Connect links are single use and short lived. Open the Better Stack panel in Jira again to get a new one.
Please let us know at hello@betterstack.com. We're happy to help! 🙏
We use cookies to authenticate users, improve the product user experience, and for personalized ads. Learn more.