Send Yocoolab feedback threads to Jira
Turn a pinned comment into a Jira Cloud issue with one click, with the screenshot attached. Status stays in step once you add the webhook.
Availability, October 2026
Overview
When a team member clicks Send to Jira on a thread, Yocoolab creates an issue in the Jira project mapped to that repository, with the comment, the element’s selector and the screenshot attached.
- Replies: messages added in Yocoolab are posted to the issue as Jira comments. Jira comments do not come back to Yocoolab.
- Status: moving the thread on the Yocoolab board transitions the Jira issue. With the webhook below, a status change in Jira updates the Yocoolab thread.
- Pull requests: when a PR number and link are recorded on the thread, they are added to the issue as a comment.
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.
Note
The list shows only repositories connected to your workspace, and connecting repositories is currently unavailable, so a workspace created today has nothing to choose here.
- 6
Set up a webhook (optional)
For Jira status changes to reach Yocoolab, register a webhook. After you save your credentials, Yocoolab shows a webhook URL for your workspace. It looks like this and includes your workspace’s secret, so keep it private:
https://<yocoolab-backend>/webhooks/jira?secret=<your workspace secret>In Jira, go to Settings → System → WebHooks, create a webhook with that URL, and select the Issue updated event.
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 comment, the element’s selector and the screenshot attached.
Reference
API endpoints
| 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 extension for Chrome, Edge or Firefox and pin your first comment on a live page.
No seat fees in beta. Every team member included — designers, developers, PMs, stakeholders.