Customer Scenario 

The customer has a Sync setup for a Team where there are three defined Create alert rules, if for example the first rule creates an alert for ISSUE-12345 the second and third cannot create additional alerts on that issue as they trigger a loop detection and are discarded.

Multiple alerts should be made possible when needed without triggering loop detection. 

From OpsGenie: Problem Definition

Currently, the new JSM cloud integration allow creation of one alert per JSM issue. If the integration includes rules to create new alerts for every comment, the rule would work for the first comment but we see the below messages in our logs:

[incoming][jira-service-management-cloud]Execution of action[create] is finished with status[DISCARDED]. Execution message: [Loop is detected. Execution is discarded!]

Suggested Solution

The new integration should allow creation of multiple alerts without hitting the loop detection mechanism when unique aliases are used.

Workaround

No known workaround at this time.