centralcloud/oncall-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update escalation step wording (#3854)

Browse source 
Fixes https://github.com/grafana/oncall/issues/3828 (was debugging some
code around, simple update)
This commit is contained in:
Matias Bordese 2024-02-08 12:04:35 -03:00 • committed by GitHub
parent d64ca29756
commit cb48842e49
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
engine/apps/alerts/models/escalation_policy.py
View file

@ -117,7 +117,7 @@ class EscalationPolicy(OrderedModel):
"Start {{importance}} notification for schedule {{schedule}}",
"Notify users from on-call schedule",
),
STEP_FINAL_RESOLVE: ("Resolve incident automatically", "Resolve incident automatically"),
STEP_FINAL_RESOLVE: ("Resolve alert group automatically", "Resolve alert group automatically"),
# Slack
STEP_FINAL_NOTIFYALL: ("Notify whole Slack channel", "Notify whole Slack channel"),
STEP_NOTIFY_GROUP: (

2
engine/apps/base/models/user_notification_policy_log_record.py
View file

@ -203,7 +203,7 @@ class UserNotificationPolicyLogRecord(models.Model):
self.notification_error_code
== UserNotificationPolicyLogRecord.ERROR_NOTIFICATION_POSTING_TO_SLACK_IS_DISABLED
):
result += f"failed to notify {user_verbal} in Slack, because the incident is not posted to Slack (reason: Slack is disabled for the route)"
result += f"failed to notify {user_verbal} in Slack (reason: {self.reason})"
elif (
self.notification_error_code
== UserNotificationPolicyLogRecord.ERROR_NOTIFICATION_POSTING_TO_TELEGRAM_IS_DISABLED