Jira

Choose the Jira site, project, issue type, and field mapping. Define whether a repeated failure updates an existing issue or creates a new one, and who decides when the issue is resolved.

Limit the integration identity to the intended project and permitted issue actions. Confirm required fields, issue security, attachments, and whether comments may expose test evidence to a wider audience.

Create a clearly labeled test issue with sanitized evidence. Repeat the same event and verify your duplicate-handling rule. Check that the issue contains a useful link and reproduction context without secrets.

A rejected issue may indicate a required custom field, an unavailable issue type, or a permission mismatch. Inspect the provider response without logging credentials or private descriptions.

Disable the trigger, revoke credentials, and remove test issues under your retention policy. Keep the disposition of real defect records in the normal Jira ownership process.