Jira
Create Jira issues from failed Drizz tests, and the shared-token attribution caveat that applies to every generated ticket.
Drizz creates a Jira issue from a failed test.
What it does
Creates a Jira issue when a test fails
Authentication
A single shared token for the whole organization
You can set
The assignee
You can't set
The reporter
Watch out
Every ticket is reported by whoever connected the integration, not by whoever ran the test
Prerequisites
Drizz organization account
A Jira project to file issues into
A Jira account whose token authenticates the integration — a service account, not a personal account
Setup details from your Drizz contact
Attribution
The integration authenticates with one shared token. Every issue is attributed to the account that connected the integration, regardless of who triggered the run.
Assignee
Yes
Whoever you configure
Reporter
No
The account that connected the integration
Consequences:
The reporter is identical on every ticket
Do not key filters, dashboards or automation on it
Run context is not carried into any Jira field
Put the triggering user, the test plan and the report link in the summary or description
A personal account becomes the permanent reporter
Connect with a service account
Common mistakes
Filtered Jira by reporter to find your failures
Every Drizz ticket has the same reporter
Connected the integration with a personal account
Every generated ticket is attributed to you, indefinitely
Expected the triggering user's name on the ticket
It isn't carried through. Put it in the description
Assumed one ticket per unique failure
Deduplication behavior isn't confirmed
Next
When a step fails — triaging before you file
Statuses — what counts as a failure
CI/CD — triggering runs from a pipeline
Last updated: 6 August 2026
Last updated
Was this helpful?