Troubleshooting
Fix common connection, push, and permission issues.
Connection checks fail
Invalid API token
- Confirm the email matches the Atlassian account that owns the token.
- Create a new API token and paste it carefully (no spaces).
- Confirm the site URL is your Cloud host, typically ending in
.atlassian.net.
checklist
✓ https://your-company.atlassian.net (no trailing path)
✓ Email used for Atlassian login
✓ Fresh API token from id.atlassian.com
✓ Account can access the Jira sitePush errors
Wrong project key
Use the exact project key from Jira (for example QA or PAY), not the project name. Keys are usually uppercase.
Permissions
- Create Issues in the target project
- Browse Projects
- For Xray types, permission to create the relevant issue types in that project
Issue type
If create fails with an issue type error, pick a type that exists in the project (often Test when Xray is installed, or another type your admin configured).
Xray warnings
- Credentials not configured: add Client ID and Secret under Xray Setup.
- Test Set / Execution skipped: tests may still exist in Jira; fix Xray credentials and retry grouping options on a new push if needed.
Plan and access
- Push and advanced coverage require Pro. Check Pricing.
- Free daily generation limits reset on a rolling window — wait or upgrade if you hit the cap.
Still stuck
Capture the exact error message from settings or the Push drawer, the project key, and whether Jira / Xray checks pass. Review FAQ for data and security questions, or How Push Works for expected behavior.