Feature Releases

RETROSPECTIVES

Required questions in the custom questionnaire must be completed before publishing a retrospective. (INC-144)

INCIDENT RESPONSE

• Enhancements to the Incident Summary (INC-142)

  • The section titled “Resolution Time” now displays timestamps corresponding to the first time the incident was resolved as well as the most recent time the incident was resolved.

  • Incident timestamps are now grouped by type and display the start and end timestamps (date/time). Tooltips state the event associated with a particular timestamp.

SLACK INTEGRATION

• Ability to send comms from an incident channel in Slack (OBI-1234)

  • Use the Slackbot command /blameless send comms to send a new email or Slack message. Find recipients based on their Slack user ID or email address.

COMMSFLOW

• Trigger webhooks or CommsFlow when a runbook is attached to an incident. (OBI-1099)

Bug Fixes

FOLLOW-UP ACTIONS

• Follow-up action Jira project uses the Jira global settings, not incident-type specified settings (INC-255)

  • Issue: When adding follow-up actions to a retrospective, they don't default to the Jira board that was configured for that incident type, instead inserting the one from the Jira Global Settings.

  • Fix: Now the default Jira project for a new follow-up action is pulled from the selected incident type instead of the Jira global settings.

RELIABILITY INSIGHTS

• Unable to display the analysis section of a Retrospective in Reliability Insights (VADER-258)

  • Issue: The analysis section of a retrospective was not properly supplied when selected as a field to be displayed or analyzed in a dashboard tile.

  • Fix: The entire analysis section of a retrospective is now provided in its entirety in its native markdown format.