TL;DR: Following our last update that lets you manage incidents directly from MS Teams, Jira Service Management ChatOps now brings on-call schedule notifications and dynamic schedule aliases directly into Microsoft Teams.
Ever wondered who’s on call right now, then spent several minutes searching calendars or messaging the wrong person?
With Jira Service Management ChatOps for Microsoft Teams, we’re making sure your team always knows who’s on deck without the chaos. Get ready for real-time on-call change notifications directly in your Teams channel. And the best part? You can now summon help like a wizard
What’s new
- On-call schedule notifications: Receive channel notifications when a schedule starts or ends.
- Dynamic aliases: Mention an alias such as
!payments-oncall to reach whoever is currently on call. No more guessing who’s on duty. Configure once, then simply use !alias-name ➡️ the bot replies with @ on-call human . Fast, simple, effective. - Automatic handoffs: The alias updates automatically when the rotation changes.
- Live coverage lookups: Check who is on call directly from Microsoft Teams.
What is an on-call alias?
An alias is a dynamic nickname for whoever is currently on call; not a specific person. Your team configures an alias once when connecting a schedule to a Teams channel. For example, you might create !payments-oncall or !tier1-support.
After setup, team members can use the alias in the channel to notify the current responder. When the rotation changes, the alias automatically resolves to the new on-call person, so nobody needs to update the channel manually. Learn more about alias here.
Why this matters
Most engineers do not continuously monitor their on-call calendars; they rely on timely notifications and clear handoffs. Without them, engineers can be paged unexpectedly, handovers can be missed, and alerts may go unanswered.
Proactive notifications and dynamic aliases reduce that uncertainty. They help teams reach the right person faster, improve time to engage, and keep on-call information visible where responders already collaborate.
How to get started
Step 1: Connect or Update Microsoft Teams on Jira Service Management
- In Jira Service Management, open Settings.
- Go to Jira settings and open Chat and video tools.
- Under Microsoft Teams, select Connect or Unlock for new features if an existing integration needs to be updated OR connected a new Teams instance if a new user.
- Complete the required tenant and permission setup.
Step 2: Start the setup flow in Teams
- Open a public Teams channel where your team collaborates.
- Mention the Atlassian ChatOps bot and enter
oncall i.e. use the command @Atlassian ChatOps oncall . - Select Connect a schedule when prompted.
Step 3: Configure the schedule and alias
- Select the JSM site.
- Select the on-call schedule.
- Choose the notification events, such as shift start and shift end.
- Enter an alias, such as
!oncall or !payments-oncall. - Save the configuration.
Once connected, the bot posts a confirmation in the channel. Team members can then use the alias to reach the active on-call responder.
Useful ChatOps commands
Action | Command or interaction |
|---|
Start on-call setup | @Atlassian ChatOps oncall to do on-call set up |
Check current coverage | @Atlassian ChatOps whoisocall to find out who is oncall for the attached schedule |
Reach the active responder | Type the configured alias, such as !payments-oncall |
What all can you do?
On-call schedule notifications: Automatically receive channel notifications when a schedule starts or ends.
Dynamic aliases: Mention an alias such as !payments-oncall to reach whoever is currently on call.
Live coverage lookups: Check who is on call directly from Microsoft Teams.
You can use this feature in public channels only. All you need to ensure that you provide the permission to Jira Service Management ChatOps bot for the team you are a member. These permissions ensure the bot can function correctly in those channels once it's added. This is a just one time permission to be given by user, that’s all.
Please leave any feedback below in the comments, so that we can continue to improve the product experience.
Thank You!
