Problem statement:
Currently, the Grafana integration in Opsgenie translates the alias to the rule ID from Grafana which is sending the payload over and thus, breaks the field mapping required for automating Create and Close action filters.

Expected solution:
The Integration should not let Grafana rule id to be overwritten for the mapped alias field/value in Opsgenie for the Create/Close action filters to work as expected.

If Opsgenie built the Grafana integration similar to other integrations and worked with Grafana to switch the method they are using to send payloads. Then it will allow the user more control over selecting the alias they want to use.