Fine‑grained control over Atlassian ChatOps notifications and alerts in Microsoft Teams

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • Component/s: Channel - Chat
    • None
    • 1

      Problem

      Currently we cannot properly control which Jira/JSM events Atlassian ChatOps sends to Teams channels. This creates a lot of noise, important alerts get lost, and different teams cannot tailor notifications to their workflows.

      Proposed Solution

      Add advanced notification controls for Teams channels, including:

      • Rule‑based filters: Configure which events are sent based on fields like issue type, status, priority, request type, SLA, etc.
      • Content control: Choose which fields appear in the card (summary, status, priority, assignee, SLA, etc.) and allow compact vs detailed layouts.
      • Frequency controls: Group/aggregate rapid updates on the same issue and optionally limit the rate of messages per channel.
      • Admin visibility: Let site/project admins see and manage all ChatOps rules and connections in one place.

      Value

      This will reduce noise, make key alerts more visible, improve on‑call and support efficiency, and increase adoption of Atlassian ChatOps with Microsoft Teams.

              Assignee:
              Unassigned
              Reporter:
              Rohit Mane
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: