// integrations
Connecting Jira to OneClik
Push captured issues straight into a Jira project as real tickets — with the page URL, browser, and reporter attached, and a link back to the full developer trace.
On this page
Before you start
- A Jira Cloud site — your-site.atlassian.net. OneClik only connects to Atlassian Cloud, not Jira Server or Data Center.
- An Atlassian account with permission to create issues in the target project.
- A OneClik workspace admin role — the connection page is admin-only.
Generate an API token
Open your Atlassian account security settings
Sign in at id.atlassian.com, then go to Security → API tokens (directly: id.atlassian.com/manage-profile/security/api-tokens).
Create the token
Select Create API token, give it a label your future self will recognize — OneClik integration works well — and confirm.
Copy it immediately
Atlassian shows the token exactly once. Copy it now — you'll paste it into OneClik in Phase 3.
Gather your site details
Find your site's base URL
This is the address you use to open Jira day to day — for example https://acme.atlassian.net. OneClik only accepts an Atlassian-hosted site:
| Rule | Why |
|---|---|
| Must end in .atlassian.net or .atlassian.com | Prevents the base URL from being pointed at an internal or unrelated server. |
| Must use https:// | The API token travels with every request. |
| No username or password embedded in the URL | Credentials belong in the token field, not the address. |
Confirm the account email
Use the same email address the API token in Phase 1 belongs to — Jira authenticates each request as that email plus that token together, not the token alone.
Connect in OneClik
Open the Jira integration settings
In OneClik, go to Settings → Integrations → Jira and enter the base URL, email, and API token from Phases 1 and 2.
Pick a project from the dropdown
Once all three fields validate, OneClik asks Jira which projects the account can see and fills the dropdown automatically:
Project — select where issues will be created
Can't find a project? Type its key directly — the same key shown in the URL of any of its issues, e.g. the OC in acme.atlassian.net/browse/OC-142.
Save the connection
Select Connect. The base URL, email, and token are all verified against Jira before anything is saved, so a typo or an expired token is caught immediately rather than at the first real push. New issues are created as the Bug issue type by default.
Verify it worked
Check the connection status
The Jira settings page shows a live status pulled directly from Jira's /rest/api/3/myself endpoint, so a revoked token or a changed password shows up the next time anyone opens the page — not just at save time.
Send a test issue
Push any existing OneClik issue to Jira and open it in the connected project. The ticket carries the page URL, browser, reporter, and timestamp, plus a link back to View developer information — the console logs and network trace OneClik keeps in its own portal rather than copying into Jira.
Troubleshooting
"Token invalid or revoked"
The API token was regenerated or revoked in Atlassian since it was saved here. Generate a new one from id.atlassian.com → Security → API tokens and reconnect.
"Token valid but lacks permissions"
The account authenticates fine but can't create issues in the selected project. Ask a Jira project admin to grant the account the Create Issues permission for that project.
"Jira base URL must be an Atlassian site"
OneClik only accepts a *.atlassian.net or *.atlassian.com address, over HTTPS, with no username or password embedded in the URL. Double-check for a trailing path or a copy-pasted redirect link — use just the site root.
The project dropdown is empty or missing a project
The account either can't browse the project or the search returned too many projects to list (the picker shows the first page and asks you to search to narrow it). Type the project key directly instead — it's the letters before the dash in any issue key, like OC in OC-142.
Jira rejected the push with a field error
The selected project may require fields OneClik doesn't send (a custom mandatory field, for instance), or the Bug issue type may not exist on that project's workflow. Check the project's issue type scheme in Jira, or route captures to a project that accepts a plain Bug with just a summary and description.
OneClik · Integrations documentation
Next upSlack integration →