Automatically open a tracked issue when a critical alert fires or an unexpected configuration change is detected.
Create an API token from your Atlassian account, scoped to a service account rather than a personal login where possible, so the integration doesn't break if that person leaves.
Enter your Jira site URL, the API token, and the project key issues should be created in.
Most teams create a Jira issue for Critical alerts and flagged configuration changes, but route Warning-level alerts to Slack only, to avoid flooding a backlog with noise.
Set the default issue type, priority mapping (Zynty severity to Jira priority), and any required custom fields your project enforces, so tickets are created without needing manual cleanup afterward.