Real-world examples of the connector in practice.
Catch critical bugs the moment they're filed
Engineering and support teams often need the whole team to know the instant something urgent lands in Jira - not just the assignee. A Global or Project notification rule scoped to a priority filter turns that into something automatic rather than something someone has to remember to do.
-
A Jira admin or project admin creates a rule filtered to Critical-priority bugs and points it at a Teams channel - e.g. an "Incidents" or "On-Call" channel the whole team already watches.
-
The moment a matching work item is created, the channel gets a card with the summary, priority, and reporter, with no one needing to check Jira or wait for someone to post it manually.
-
Because the rule is admin-configured rather than personal, it applies consistently to the whole team - new hires are covered automatically without needing to set anything up themselves.
-
If the audience is outside the Jira tenant's own Microsoft org (e.g. an external partner team), the same rule can deliver via a webhook instead of the bot, since webhook delivery doesn't require the recipient's tenant to be connected.
See: Setting Up Global & Space Notifications and Notification Destinations.
Discuss a work item without leaving the conversation
Some work items need more than a status update in a channel - they need an actual conversation, with a place for that conversation to live and be found again later. A discussion channel gives a work item its own dedicated space in Teams without anyone having to set up a channel by hand.
-
From the work item's "..." menu, a user creates a discussion channel in a couple of clicks, naming the Teams team it should live in - the channel itself is named and described automatically after the work item.
-
Everyone relevant to the item - assignee, reporter, watchers - gets pulled into the conversation via an @mention in the channel's first message, so nobody has to be manually invited.
-
Because each work item can only have one discussion channel, the whole team ends up in the same conversation instead of it fragmenting across several ad-hoc chats.
-
Anyone can jump back into that conversation later directly from the work item's Microsoft Teams panel, without needing to remember which channel it was or search for it in Teams.
See: Creating Discussion Channels.
Never miss a deadline
Status changes and comments are covered well by notifications, but deadlines are a different kind of thing to track - they need to surface at a specific moment, not just when something changes. Reminders exist for exactly that gap.
-
Anyone can set a one-time reminder on a work item directly from its Microsoft Teams panel, picking a delivery time in their own local time zone and an optional note to include.
-
For due dates specifically, a personal notification rule's "Upcoming due date" event can notify automatically a chosen number of days beforehand, so there's no need to remember to set a reminder by hand for every item with a deadline.
-
The reminder arrives as a message in the user's 1:1 chat with the bot, separate from channel noise, so it doesn't get lost in unrelated conversation.
-
The same thing can be set up conversationally - "remind me about this issue tomorrow at 9am" - through the Teams Connector Rovo Agent instead of opening the form.
See: Work Item Reminders, Notification Rule Reference, and Teams Connector Rovo Agent.
Give stakeholders a live view without Jira access
Not everyone who needs visibility into a project's progress has (or wants) a Jira license. A Jira tab turns a saved filter into a live table that lives directly inside a Teams channel or chat, so status is always one click away for whoever's in that conversation.
-
A saved Jira filter is added as a tab in a Teams channel, with the option to choose which work item fields show as columns - useful for tailoring the view to a non-technical audience rather than showing every Jira field.
-
The table reflects live Jira data, so stakeholders are always looking at current status rather than a snapshot someone posted earlier.
-
Team members can go further than just viewing - they can create and edit work items directly from the tab, without switching to Jira at all.
See: Jira Tabs in Microsoft Teams.
Manage it all by chatting AI
Reminders, discussion channels, and personal notification rules each have their own form to fill in - useful when precision matters, but sometimes slower than just saying what you want. The Teams Connector Rovo Agent handles all three conversationally.
-
A user can ask in plain language - "notify me in Teams when a Critical bug is created in the BACKEND project" - and the agent resolves the wording into the right project, priority, and event filters and creates the rule.
-
Timezone handling for reminders is automatic - the agent looks up the user's Jira timezone rather than asking them to specify it or guessing from their words.
-
If the reminders panel or personal rules table happens to be open elsewhere while the user is chatting, it updates live the moment the agent makes a change, with no manual refresh needed.
-
For anything outside those three jobs - general Jira questions, team-level rules, unrelated tasks - the agent declines and points back to what it can actually help with, rather than guessing.
See: Teams Connector Rovo Agent.
What's next
Updated: