Jira Cloud for MS Teams - suppress notifications for automation changes

Hi, @Sarah James 

Unfortunately, the instructions provided by Rovo are not accurate — the Jira Cloud for Microsoft Teams app does not have field-level notification filtering. There's no way to exclude specific field changes from triggering Teams notifications through the app's settings. That's why your Teams admin couldn't find that menu.

However, the good news is that the fix is on the Jira Automation side, not on the Teams side:

Solution: Suppress notifications directly in your Automation rule

In your Automation rule, on the "Edit issue" action that updates the mirrored field:

1. Expand "More options"
2. Uncheck "Send notifications?"

This prevents Jira from firing the issue update event for that specific edit, which means the Teams webhook won't be triggered at all — no notification will be sent via Teams, Slack, or email for that field change.

This is the cleanest approach because:

• It's a single change in one place (your automation rule)
• No action required from individual users
• It doesn't affect notifications for other legitimate field changes
• It suppresses across all channels (Teams, Slack, email) at once

If you're using the Jira REST API instead of native automation to update the field, you can achieve the same result by adding notifyUsers=false as a query parameter on your PUT request.

Hope this helps...

Hola Sarah,

I'd suggest testing the 'Send notifications' option with one affected user before relying on it. That setting is designed around Jira's notification behavior, while the Jira Cloud for Microsoft Teams app delivers its own personal activity notifications. Because the automation still updates the issue and writes the mirrored field change into the issue history, Teams may continue to detect and report that activity.

Users can review their personal Jira notification settings by going to Teams > Jira Cloud > Notifications > Change notifications. However, Atlassian's current documentation doesn't show a field-level exclusion that would let someone suppress only changes to Org Unit while continuing to receive notifications for other custom fields. It also doesn't document a central administrator setting that applies this kind of exclusion to everyone's personal feed. 

That means the available personal settings are broader than what you need. Turning off the applicable update category may stop the unwanted messages, but it could also hide useful notifications for status, assignee, priority, or other field changes. Since these are individual feeds rather than a shared channel subscription, each user may also need to change their own preferences.

I don't see a native Jira automation condition that can mark a single issue update as invisible in the Teams app. Hiding the mirrored field from screens or restricting who can edit it won't prevent the underlying update from appearing in the issue history, so those changes are unlikely to affect the Teams notification.

The closest public suggestion I found asks Atlassian to integrate Jira notification schemes with Microsoft Teams. It doesn't specifically request custom-field exclusions, but it addresses the broader limitation that Teams notifications can't be centrally controlled via Jira's standard notification configuration. You may want to vote for and watch it, and add your field-level automation use case in a comment. 

For now, I believe the practical choices are to reduce the relevant personal notification category in Teams or leave those notifications enabled until Atlassian adds more granular filtering. I'd also report the inaccurate Rovo guidance through its feedback option so Atlassian can review the response.

Thanks,

James