Feature Release

INCIDENT MANAGEMENT

Pagerduty Services Integration (48 / YD-163 & YD-255 )

Pagerduty services can be mapped to an incident when starting a Blameless incident via Slack or the Blameless web UI. A Pagerduty alert is automatically triggered for each added Pagerduty service if the auto-trigger option is enabled for the corresponding incident type. 

Having the Incident/Retrospective open in a new tab when clicking on Incidents/Retrospective List Page (INC-174)

When on the Incidents / Retrospective page, clicking on an incident / retrospective will open the record on the same tab. The User needs to right-click on the Incident/Retro to open the record in a new tab.

Bug Fixes

RETROSPECTIVES

Retrospective Collaborators" Section of the Retrospective appears not to populate even when retrospective roles are assigned via slack (INC-87)

Issue:

The Retrospective role assigned via Slack does not appear where expected. 

Fix:

There was an unrelated component that was mutating a data structure before it rendered the "retrospective collaborators" section. 

Users can still save the Custom Questions in Retrospective even if JSON Schema has the field set as required (INC-163)

Issue:

JSON Custom "Required Questions" (with an asterisk) don’t seem to be required anymore, meaning the user can still click SAVE even if the required field is not completed.

Fix:

The logic in the associated field has been fixed so that Required Questions are required and must be completed before saving.

Retrospective comment mentions still show as "Blameless Postmortem" with the Postmortem link via the Slack notification (INC-80)

Issue:

Retrospective comment mentioned shows as ‘postmortem’ and has PM link as shown in screenshots.

Fix:

When someone comments in a retrospective, the message will now notify the customer using the correct terminology ("Retrospective"), as well as referencing the API using the correct term.