April 1, 2022

Feature Releases

SWIMLANES FOR MICROSOFT

Swimlane functionality in Microsoft Teams

Introduces the support for Swimlanes in Microsoft Teams. When a Swimlane is created from within an Microsoft Teams incident channel, the following commands can be performed within a swimlane:

Show list of available commands only supported in a swimlane
All tasks commands
Apply Tags
Apply Timeline events
Capture data as highlight into the incident timeline
Create follow up actions
Close and re-open a swimlane

COMMSFLOW

New generic ways to define recipients for automated messages in CommsFlow

Provides new ways to generically define recipients for automated messages in CommsFlow:

User emails and mailing lists, in addition to the emails provided by registered Blameless users
Slack user groups
Target users via email, SMS, Slack, and Teams based on their Blameless incident roles

Send messages if incident has matching tags

As part of the Filter Triggering in their Flows, users have additional flexibility to control when to send messages for incidents based on the presence or absence of selected tags in specific tag categories.

NOTE
Those tag categories and tags are user defined per incident type settings.

INCIDENT MANAGEMENT

Customizable “End of Customer Impact” timestamp

Configurable “End of customer Impact” timestamp when incident status changes to a status other than "RESOLVED (default)" using a pull-down list to select one of ANY supported incident statuses. This is configurable at the incident type level.

Investigating
Identified
Monitoring
Resolved (default)

NOTE
“End of Customer Impact” defines when the end of customer impact date and time is initialized for an incident. Users can modify it manually afterwards through the Blameless web UI.

Statuspage components organized by component groups when sending external incident communications

When sending external communication updates to Statuspage manually from the Comms Tab for a selected incident in the Blameless web console (UI), users can now find and select the appropriate Statuspage components which may be organized by component group.

Bug Fixes

SLACK

Slack as an option appearance issue for Internal Comms (OBI-937)

Issue:

Some customers are not seeing Slack as an option for internal comms.

Fix:

The workflow id was not set for reminder execution flows; that has been corrected.

Slack automatic invitation issue after Slack Enterprise Grid migration (BOTS-354)

Issue:

Some customers have reported that bot users are not getting automatically invited into the incident channels, when they have been prior. The only update, in terms of what changed, is that both have migrated to Slack Enterprise Grid.

Fix:

Re-adding the Custom Bot ID (not Blameless Bot) to after the upgrade for Slack Enterprise clears the issue.

INCIDENT MANAGEMENT

Custom Questions throw errors when required (INC-64)

Issue:

In the JSON schema when a question is marked required standalone, the UI on the Overview page displays errors.

Fix:

Complete the questionnaire before trying to save.

COMMSFLOW

Unable to add roles in the Incident roles field for Email in the flow creation wizard (OBI-1012)

Issue:

If a user only selected an incident role, they would get the following error message:

Invalid Email Address. This happened due to Blameless expecting at least one email address.

Fix:

Expand the validation to require at least one email address or incident role.