The "Contains" and "Matches (Regex)" operators don't work as expected for the Responders component in Jira (Legacy) integration

XMLWordPrintable

    • 1
    • Severity 2 - Major

      Issue Summary

      In the Jira (Legacy) integration settings, under the "Create Jira issues for Opsgenie alerts" section, when creating an alert filter with the component "Responders", the "Contains" or "Matches (Regex)" operators don't correctly match the alert values.

      Steps to Reproduce

      1. Check the option "Create Jira issues for Opsgenie alerts" under the settings of an existing Jira (Legacy) integration.
      2. Edit the filter rule and select "Alerts matching all the conditions" or "Alerts matching at least one condition"
      3. Select "Responders" as the component, the operator "Contains", and enter the value you want to test.
      4. Save the changes
      5. Create a new alert in Opsgenie including a responder that should match the filter recently created
      6. Validate the Activity Log of the alert and confirm that the action "Sent [createIssue] action to Jira" was not logged.
      7. Go to the integration settings again and change the operator from "Contains" to "Not Contains". Keep the value as is.
      8. Create a new alert and add the same responder from the previous step
      9. Validate the Activity Log of the alert and confirm the action "Sent [createIssue] action to Jira" appears.

      Expected Results

      Assuming the alert contains a Responder like "John Doe", the filter "Responders Contains John" should work and execute the respective actions.

      Actual Results

      If the alert contains a Responder like "John Doe", the filter "Responders Contains John" doesn't trigger the respective actions.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Diego Vizcarra
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: