Summary: 

Use case: Customer has 3 separate SNow environments connected to Opsgenie, with incident data replicated across 2 (think Prod SNow feeding a dev and staging SNow instance, with incidents mirrored in these secondary SNow accounts). As of now - it is difficult to force an alert created through one of these integrations to only send updates back through that same integration (in the case where these are global integrations). It would be nice to add the ability to force alerts to only send updates back through their creating integration, or add the ability to filter for when to send those updates.

Workaround:

There are a few possibly workarounds:

1) Set these integrations up as team-scoped - this would allow for a flow where updates made to an alert would only send outbound through integrations also assigned to that team. This provides some separation.

2) Modify the web service scripts in SNow to filter - then you could add a tag to the alert in OG, and filter for that tag in SNow, and essentially discard any updates not matching the tag for that environments

3) Use a separate Opsgenie account (or, if on Enterprise, an Opsgenie sandbox account) to hook into these non-prod SNow accounts. Reach out to support to enable to your sandbox account (if on Enterprise).