This is How Blameless Integrates with JIRA

Key workflows

  • A Slack channel that acts as your war room
  • A video conference bridge for synchronous communication
  • A corresponding JIRA ticket

A typical incident lifecycle in JIRA and Blameless

Benefits of integrating JIRA and Blameless

  • Eliminate toil: Ensure real-time incident data and follow-up actions are captured in the moment with Blameless, while seamlessly syncing data into JIRA as your system of record. No more copying and pasting things like incident priority and action items between tools.
  • Create follow-up actions: Add in tasks as you think of them during an incident, as well as afterwards. Blameless will associate follow-up actions with the parent ticket.
  • Accurate reporting on follow-up item completion: Use Blameless to report on action item completion. Filter on incomplete action items by incident, tag, customer, and more.
  • Better communication between engineering teams and product: By ensuring that all follow-up actions are captured in both JIRA and Blameless, you can sort through action items to determine where development efforts would be best spent. This also helps product prioritize accordingly.

Best practices of using JIRA with Blameless

  • Add action items to Blameless first. This helps keep everyone on the same page, drives real-time coordination, and prevents tickets falling through the cracks. It also keeps all information associated with an incident in one place.
  • Create tagging in Blameless that matches your JIRA tags. Having a standard nomenclature helps minimize cognitive load between tools. Additionally, using the same vernacular between development and product helps communication.
  • Add follow-up tasks as you think of them, and revise and assign during the retrospective. Nobody wants to forget an action item. Add action items to the list of follow-ups as soon as you think of it. After all, an idea might never become quite as fresh again in your head as during an incident itself. You can always refine and assign later once you have a better idea of how to prioritize.




Giving you all you need to know about Site Reliability Engineering.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Importing Assets UE5

Cere Network: project review

HTML Injection via user agent leads to website distortion revealing backend code.

Aleo is a project with unique solutions

Why is immutability matters?

Two-Factor Authentication using Face Recognition

Control your Windows system remotely via voice

Crack those CAPTCHAs with opencv and python

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


Giving you all you need to know about Site Reliability Engineering.

More from Medium

RediSearch — A tour of how few commands work — Part 1

5 best practices for building cloud-native permissions

A proposal for an internal development platform implementation

Gitops agent to create the resources specified in Git

How long should I wait to retry a failed async job? Here is the Exponential backoff