Problem Statement
The Sentry webhook integration for issue alerts returns key information on the event that was received for an issue in a project that matches an issue alert rule [ref]. Unfortunately, only the name (label) of the issue alert rule is returned which is not enough to uniquely identify the issue alert rule because many issue alert rules can share the same name. I'd like if the issue alert rule ID was also returned.
Solution Brainstorm
The webhook integration for issue alerts already returns a json object with details for the issue_alert [ref]. Adding a field for the id on that object could make sens, e.g.
"issue_alert": { "title": "Very Important Alert Rule!", "id": 123456, "settings": [ { "name": "channel", "value": "#general" } ] }
Product Area
APIs
┆Issue is synchronized with this Jira Improvement by Unito
Problem Statement
The Sentry webhook integration for issue alerts returns key information on the event that was received for an issue in a project that matches an issue alert rule [ref]. Unfortunately, only the name (label) of the issue alert rule is returned which is not enough to uniquely identify the issue alert rule because many issue alert rules can share the same name. I'd like if the issue alert rule ID was also returned.
Solution Brainstorm
The webhook integration for issue alerts already returns a json object with details for the
issue_alert[ref]. Adding a field for theidon that object could make sens, e.g."issue_alert": { "title": "Very Important Alert Rule!", "id": 123456, "settings": [ { "name": "channel", "value": "#general" } ] }Product Area
APIs
┆Issue is synchronized with this Jira Improvement by Unito