We have multiple services connected to the same Slack Notification Channel.
Historically, when an incident was reassigned between those services, the existing Slack incident card was updated, including the Service field. Recently, without any configuration changes on our side, PagerDuty began posting a second incident card for the same incident when the service changes.
Interestingly, subsequent incident updates (we use the Thread incident updates option) are still applied to the original Slack post rather than the newly created one. This suggests that PagerDuty is still able to correlate the Slack message with the incident, making the additional post redundant.
Expected behavior
- Reassigning an incident between services that are connected to the same Slack Notification Channel should update the existing Slack incident card, including the Service field.
Actual behavior
- A second Slack incident card is posted when the service is reassigned.
- Subsequent incident updates, such as status changes, continue to update the original Slack post.
Could you confirm whether this is an intentional change or a regression?
