• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Operations - Sync
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem

      Currently, the alias field in Opsgenie alert rules is automatically set to the issue key by default. This behavior can lead to unintended deduplication, especially when multiple syncs generate alerts for the same issue. Many users are unaware of this mechanism as the alias property is hidden by default.

      Suggested Solution

      To enhance usability and avoid confusion, we propose the following improvements:

      • Show the alias field by default when configuring an alert rule.
      • Provide an inline tooltip explaining its impact on deduplication.
      • Suggest alternatives, such as customizing the alias to ensure unique alerts.
      • Provide a direct link to Atlassian documentation explaining alias behavior. 

      Why This Is Important

      • Prevents accidental alert deduplication.
      • Reduces confusion for new users configuring syncs.
      • Improves transparency of automation behavior.

      Workaround

      • We can expand the Show all properties within the intended Sync

            [JSDCLOUD-16270] Improve Alias Field Transparency & Warnings in Opsgenie Alert Rules

            There are no comments yet on this issue.

              Unassigned Unassigned
              ssamal@atlassian.com Shakti
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: