Jira issues not creating: fix the connection, then the permissions
Creating a Jira issue from an AllStak error fails, or closing the Jira issue never resolves the linked error. Both have short, specific checklists.
What this looks like
You open an error in AllStak, choose to create a Jira issue from its action menu, fill in the project key, summary, and issue type — and the creation fails. Or it succeeds, but later closing the Jira issue does not resolve the linked AllStak error the way it should.
These are two different failure paths: issue creation depends on the OAuth connection an organization admin set up and on permissions inside Jira; auto-resolve on close depends on the inbound webhook configured per-integration being reachable from your Jira site.
Common root causes
Jira not connected (or token revoked)
Jira connects through Atlassian OAuth, set up by an organization admin from the Integrations page. If it was never connected — or the Atlassian side revoked the authorization — every create fails.
Jira-side project permissions
The connected Atlassian account must be able to create issues in the target Jira project. A wrong project key, a project the account cannot see, or a missing Create Issues permission all fail on Jira's side.
Invalid issue type for the project
Issue types vary per Jira project. Choosing a type the target project does not offer (or one with required custom fields) makes Jira reject the creation.
Auto-resolve webhook unreachable
Closing the Jira issue resolves the linked error only when Jira's done-category transition reaches the inbound webhook configured per-integration. If that webhook is unreachable, links go stale silently.
Step-by-step diagnosis
Fix creation first, then verify the resolve-on-close loop separately.
- 1
Confirm the integration is connected
Have an organization admin open the Integrations page and check the Jira card. If it is disconnected or shows an authorization problem, run the Atlassian OAuth flow again and approve the prompt.
- 2
Retry creation from the error's action menu
Open an error in AllStak and create the issue from its action menu, double-checking the Jira project key, summary, description, and issue type. Note the exact error message if it fails — it usually names the Jira-side cause.
- 3
Check permissions inside Jira
In Jira, confirm the connected account can browse the target project and create issues in it, and that the chosen issue type exists there without mandatory custom fields. Fix the permission scheme or pick another project/type.
- 4
Reconnect after Atlassian-side changes
If the connecting admin left, the account changed, or apps were pruned in Atlassian admin, the stored authorization may be dead. Reconnecting through OAuth from the Integrations page restores it.
- 5
Verify the auto-resolve loop
Create a test issue from a test error, move it to a done-category status in Jira, and confirm the linked AllStak error resolves. If it does not, check the inbound webhook configured for the integration is reachable from your Jira site.
Prevent it from recurring
- Connect Jira with a service account rather than a personal one, so departures do not break the integration.
- Document the target Jira project key and issue type your team uses for production errors.
- After any Jira permission-scheme change, test one create-from-error before relying on it.
- Periodically close one linked test issue to confirm the auto-resolve webhook still works.
Still stuck?
If creation fails with the connection healthy and Jira permissions confirmed, email [email protected] with your organization name, the Jira project key, and the error message you see — and check the AllStak status page for any platform-side issues first.
Frequently asked questions
Who can connect the Jira integration?
An organization admin connects Jira through the Atlassian OAuth flow from the Integrations page. Once connected, team members can create issues from errors.
Why does closing the Jira issue not resolve the AllStak error?
Auto-resolve requires the error to be linked to the issue and Jira's done-category transition to reach the inbound webhook configured per-integration. Check that the webhook is reachable and that the issue actually moved to a done-category status.
Does AllStak create a Jira issue for every error automatically?
No — issue creation is deliberate, from an error's action menu. That keeps Jira for work that needs engineering ownership while noisy or transient errors stay in AllStak as triage-only signals.
Which Jira is supported?
The integration connects a Jira Cloud site through Atlassian OAuth, with tokens kept server-side.
From alert to tracked work
Connect Jira once, create issues from the errors that matter, and let done-category transitions resolve them in AllStak. Start free.