Jira
Leak events are turned into Jira issues.
How it works
The connection uses an API token, and the token carries the account’s own permissions. Issues are opened in the project and issue type chosen during setup.
When the same event arrives a second time, no new issue is opened; a comment is added to the first one. This works through a label derived from the event identifier, visible among the issue’s labels.
State synchronisation is optional. When enabled, state changes in Jira are read and the event’s state is updated; it requires a separate approval.
Limits
Writes go only to the named project.
Issues are not closed or deleted.
The leaked value itself is not written to the issue.
Setup
The setup steps are in the panel, on the integration’s own screen. What to do on the provider side and which value goes where is written there.