I have set up a mirrored custom field for a field of a type that cannot be selected for view or grouping in Jira Plans. The field is not meant to be seen or updated by users and I have an automation that populates it or changes it when its mirror is updated. My problem is that the automation hits the webhook for Jira Cloud for Teams and sends people notifications of the update of the field. This looks like annoying spam and defeats my purpose of low visibility.
I checked against Rovo and it suggested the instructions below. I had the Teams admin check and he can't see anything like this menu path. Does anyone have experience suppressing field-level changes on the Teams end in some similar way? Since these are individual people's feeds, not a channel feed of changes, I either need a simple change they can make individually OR I need a clean way to do it at the app root level. If it makes any difference my Jira Cloud Teams app version is 2024.09.11
Very frustrated that there's not a Teams/Slack suppression available (per Rovo) like there is for email suppression. If anyone has an open ticket requesting this, I'd also love to know it so I can upvote it.
Rovo instructions:
Adjust the Teams app notification filters
In the Jira Cloud for Microsoft Teams app settings (configured per-channel or per-user), there are filters for which field changes trigger a notification. If your Teams admin can configure the app to exclude notifications for changes to Org Unit (customfield_18922), that would suppress it at the source. This is the most targeted fix.
In Teams: go to the Jira app → Notifications → edit the subscription → under Field changes, remove or exclude Org Unit.
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:
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:
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.