Hi all,
I'm setting up a Code Red / incident alerting process in Jira Service Management (JSM Ops) and trying to automatically add a Microsoft Teams bridge link to an alert's description, based on which Service is selected as the "Affected Service."
Current state: Right now, when an alert is created, the Description field only auto-populates with a link back to the originating ticket, nothing else. There's no Teams link or any service-specific info injected automatically.
What I want: When someone selects a specific Parent Service, I want the alert's Description to automatically also include that service's dedicated Teams channel/bridge link, so responders can join the call immediately.
Has anyone built something similar or knows how to dynamically append a link to an alert's Description based on a Service selection and can share how they structured the rule?
Thanks!
Hi @Timi Falusi, before the Teams link, the alert has to know which service it belongs to. Your screenshot has Source, Integration and Tags all empty, and the description is the fixed View incident line the incident-to-alert link writes. Nothing on that alert names a service.
Alert policies are where the description gets rewritten, and they run before the alert is created, so {{description}} in the policy keeps your existing line and you append to it. A policy matches on the alert's own fields though, message, alias, description, source, entity, tags, details, priority. No service among them.
So get the service onto the alert as a tag first, then one policy per service filtering on that tag and appending its link.
Does the alert show an Affected service below Tiny ID? Your screenshot stops there, and that decides whether the tag step is needed at all.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Affected services row is there and it's still an Add a service link, Tags and Source empty next to it. Nothing on that alert names the service, so the tag step stays.
Scope matters once you go to build the policy. A team alert policy only reaches an incident-raised alert when that team is the assignee or responder on the incident, so putting it on the wrong team means it never fires and nothing tells you why. A global policy carries no such condition, but it also takes precedence over a team one wherever both match. Team policies are under Teams, your team's operations, Policies, Alert policies. Global ones you create from Settings, Products, then Policies under Operations, and that needs site admin.
https://support.atlassian.com/jira-service-management-cloud/docs/what-are-alert-policies/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.