Jira Integration
Two-way sync between Yocoolab threads and Jira Cloud issues. Send feedback to Jira with one click — resolve in either tool and they stay in sync.
Overview
When a team member sends a Yocoolab thread to Jira, an issue is created with full context: screenshots with pin markers, element selectors, viewport details, and a deep link back to the live app. Comments sync between both tools, and resolving a thread in Yocoolab moves the Jira issue to Done — and vice versa.
Prerequisites
- Jira Cloud account (Server/Data Center not supported)
- Permission to generate an API token for your Atlassian account
- The email address associated with your Jira account
- Your Jira site URL (e.g.,
yourteam.atlassian.net)
Setup Steps
- 1
Generate a Jira API token
Go to id.atlassian.com/manage-profile/security/api-tokens and click Create API token.
Give it a label like "Yocoolab" and copy the token. You won't be able to see it again.
- 2
Open Yocoolab integration settings
In the admin dashboard at app.yocoolab.com, go to Settings → Integrations → Jira.
- 3
Enter your Jira credentials
Fill in three fields:
- Site URL — e.g.,
yourteam.atlassian.net - Email — the email on your Atlassian account
- API Token — the token you just generated
Click Save. Yocoolab validates the credentials by calling the Jira REST API.
- Site URL — e.g.,
- 4
Test the connection
Click Test Connection. You should see your Jira user name and a list of accessible projects.
- 5
Map repositories to Jira projects
For each Yocoolab repository, select a Jira project and issue type (e.g., Task, Bug). When a thread from that repo is sent to Jira, the issue lands in the mapped project.
- 6
Set up a webhook (optional)
For two-way sync (Jira status changes reflect back to Yocoolab), configure a Jira webhook:
In Jira, go to Settings → System → WebHooks and create a webhook pointing to:
https://api.yocoolab.com/api/v1/jira/webhookSelect the Issue updated and Issue deleted events.
Verification
Create a test thread in Yocoolab on a mapped repository. Click Send to Jira in the thread actions. The Jira issue should appear in your project with the thread title, screenshot, element context, and a link back to the live app.
API Reference
| Method | Endpoint | Description |
|---|---|---|
POST | /api/v1/jira/config | Save Jira credentials (site URL, email, API token) |
GET | /api/v1/jira/config | Get current Jira configuration status |
GET | /api/v1/jira/test | Test stored Jira credentials |
GET | /api/v1/jira/projects | List accessible Jira projects |
POST | /api/v1/jira/mappings | Create or update a repo-to-project mapping |
GET | /api/v1/jira/mappings | List all repo-to-project mappings |
DELETE | /api/v1/jira/config | Disconnect Jira integration |
Troubleshooting
Warning
401 Unauthorized — Your API token may be expired or incorrect. Generate a new token at id.atlassian.com.
Warning
403 Forbidden — Your Jira user may not have permission to access the project. Check project permissions in Jira.
Note
Site URL format — Use just the domain without https://. For example: yourteam.atlassian.net, not https://yourteam.atlassian.net.
Ready to start reviewing on the real product?
Install the free Chrome Extension, connect your tools, and start shipping faster — in under a minute.
No seat fees. Every team member is free — designers, developers, PMs, stakeholders.