Connect Jira Cloud: step-by-step guide
Files one Bug per failing test, comments on it when the test fails again, and moves it to Done when the test passes clean. This guide takes you from nothing to a verified connection, and lists the errors you can meet with their cause and fix.
Last updated:
Keep your credentials private. Never paste a token, key, password or webhook URL into a chat. Type it only in Studio → Settings → Integrations, where it is saved in your workspace's .env file and shown as dots. The same goes for an AI assistant: it can walk you through this guide, but it never needs your token.
What you need
- A Jira Cloud site, for example https://your-team.atlassian.net (Jira Cloud only; the address must be https).
- The email of your Atlassian account and an API token created with that same account.
- A project key, for example QA, whose project has an issue type named Bug.
- In that project, permission for that account to browse, create issues, add comments, create attachments and transition issues.
Get the credentials
- Open https://id.atlassian.com/manage-profile/security/api-tokens and choose Create API token.
- Name it (for example "Nexus StudioQA"), pick an expiry, create it and copy the token now. Atlassian shows it once.
- Keep it in your clipboard. Do not paste it anywhere except the Studio (next step).
Connect it in the Studio
- In the Studio, open Settings → Integrations → Connect Jira.
- Paste any link from your Jira (the home page, a board or an issue) and press Check connection. The Studio keeps the site address and the project key.
- When it asks, enter your Atlassian email and the token, and press Save & check.
- Pick the project in "Bugs go to", then turn on
JIRA_ENABLED.
Check that it works
- Check connection shows "Signed in as <your name>" and "<KEY> takes Bug tickets". The check only reads; it never opens a ticket.
- Open Settings → Integrations → Tickets and press Create test ticket. It files one ticket labeled nexus-test and is the only click there that calls Jira.
- Open that ticket in Jira and confirm it has the labels auto-generated, nexus-studioqa-automation and nexus-test. Delete it when you are done.
Common errors
| What you see | Cause | Fix |
|---|---|---|
| "That is not a link" or "A Jira link starts with https://" | The pasted text is not a full web address, or it starts with http://. | Copy the address bar while you are on your Jira site. It must start with https://. |
| HTTP 401 | The email or the token is wrong, the token expired or was revoked, or the email is not the account that created the token. | Create a new token at id.atlassian.com with the account whose email you saved, then save both again in Settings. |
| HTTP 403 | The sign-in works, but Jira says that account may not do it: usually a missing Create issues, Add comments or Create attachments permission in the project. | Ask the project admin for those permissions, or choose another project. Nexus StudioQA cannot grant them. |
| HTTP 404 | The site address or the project key does not exist, or that account cannot see the project (Jira answers 404 for projects it hides). | Paste any link from the right site and choose the project from the list. |
| "That address answered, but not with a Jira account" | The address is not a Jira Cloud site (for example a Server or Data Center address, or another web page). | Use the https://<team>.atlassian.net address of your Jira Cloud site. |
| "<KEY> has no issue type named Bug" | The project has no issue type called Bug, so no ticket can be filed. | In Jira, open Project settings → Issue types and add Bug, or choose another project. |
| "could not reach Jira (ENOTFOUND)" or "did not answer within 20 s" | This PC cannot reach the site: a typo in the address, a VPN or proxy, or no network. | Fix the address, then open the site in a browser on the same PC. Retry the check. |
| Everything checks out, but no ticket appears | JIRA_ENABLED is false; or the verdict was FLAKY or an environment verdict; or it was a sandbox run; or an open Bug already exists for that test (a repeat failure comments instead); or a Bug with the same title was filed in the last 24 hours. | Turn on JIRA_ENABLED, read "One issue per test" on the integrations page, and use Create test ticket to prove the connection. |
| A passing test does not close its ticket | The workflow has no transition named like JIRA_DONE_TRANSITION, so the ticket only gets the comment. | Set JIRA_DONE_TRANSITION to the exact name of the transition button in your workflow. |
Settings keys
| Key | What it does | Valid value | How to check it |
|---|---|---|---|
JIRA_ENABLED | Create Jira tickets for failures | true or false | Turn the integration on, then run Create test ticket. |
JIRA_BASE_URL | Jira site address | https://<site>.atlassian.net | Check connection shows the site; a pasted link fills it. |
JIRA_EMAIL | Jira sign-in email | The email of the Atlassian account that owns the token | Check connection shows "Signed in as …" with this email. |
JIRA_API_TOKEN | Jira access token (secret, saved only on this computer) | One line, no quotes, no spaces | Check connection: HTTP 401 means the email/token pair is wrong. |
JIRA_PROJECT_KEY | Jira project for Bug tickets | The project key, usually capital letters, for example QA | The project dropdown lists it; "takes Bug tickets" confirms the type. |
JIRA_DONE_TRANSITION | Jira status when test passes | The exact name of a workflow transition, matched in any case | A clean pass moves the ticket; if the workflow has no such transition it only gets a comment. |
More: all integrations, the Settings guide, troubleshooting. Other guides: Azure Boards, Slack, Microsoft Teams, Telegram, GitHub Issues.
Still stuck? Write to [email protected] with the exact error line the Studio shows. Do not include a token.