How to Send Design Feedback to Jira with Yocoolab
By Yocoolab Team
Most teams track their work in Jira, but design feedback often starts somewhere else: a comment on a design file, a screenshot in chat, a remark in standup. Yocoolab lets you pin that feedback on the live product and then send it to Jira with the screenshot attached, so the ticket starts with the context instead of a paraphrase of it.
This post explains what the integration does, what it does not do, and how it is set up. We updated it on October 10, 2026 to match the product exactly.
Availability, October 2026: New workspaces can’t map a project to Jira, Linear, Slack or Telegram yet. These integrations are set up per connected repository, and connecting repositories is currently unavailable. Workspaces that already have a connected repository can still use them. Until that changes, a new workspace can keep feedback on the Yocoolab board and send it to a coding agent with Send to Agent.
Why feedback gets lost before it reaches Jira
- •Comments on design files are not where developers look for work.
- •Screenshots pasted into chat scroll away.
- •When someone retypes feedback into a ticket, the "which element?" part is usually the first thing to go.
What the Yocoolab Jira integration does
- 1.You pin feedback on the live page. The thread keeps a screenshot, the element's selector and DOM path, its computed styles and the page URL.
- 2.You click Send to Jira on the thread. Yocoolab creates an issue in the Jira project mapped to that repository, with the screenshot attached.
- 3.Replies flow to Jira. Messages added in Yocoolab are posted as comments on the Jira issue.
- 4.Status syncs both ways once the webhook is set up. Moving a card on the Yocoolab board transitions the Jira issue, and a status change in Jira updates the Yocoolab thread.
- 5.PR links can reach Jira. When a pull request number and link are recorded on the thread, Yocoolab adds them to the issue as a comment.
If you use a coding agent, the same thread can also go to it with Send to Agent. The agent reads the element and the discussion, makes the change and moves the thread to In Review; a person signs off.
What syncs, and in which direction
| What | Direction | Notes |
|---|---|---|
| New issue | Yocoolab to Jira | Created when you click Send to Jira, with the screenshot attached |
| Replies | Yocoolab to Jira | Added as Jira comments. Jira comments do not come back. |
| Status | Both ways | Jira to Yocoolab needs the webhook below |
| PR link | Yocoolab to Jira | Posted as a Jira comment when a PR number and link are recorded on the thread |
Assignee and priority are not synced from Jira.
Setting it up
- 1.Create a Jira API token at id.atlassian.com. Jira Cloud only; Server and Data Center are not supported.
- 2.In Yocoolab, go to Settings, then Integrations, then Jira (workspace admins only), and enter your site URL, the email on your Atlassian account and the token.
- 3.Map a repository to a Jira project and choose the issue type.
- 4.Register the webhook for status sync. After you save, Settings shows a webhook URL that includes your workspace's secret. In Jira, create a webhook with that URL and select the Issue updated event.
Step 3 is the one a new workspace can't complete today: the mapping list shows only connected repositories, and connecting repositories is currently unavailable. Full setup steps are on the Jira docs page.
The bottom line
For workspaces that can use it, the integration gets visual feedback into Jira with the screenshot attached and keeps status in step between the two tools. The element context stays on the Yocoolab thread, one click away, for whoever picks up the ticket, and for your coding agent.
Review on the real product
Pin comments on any live page with the Yocoolab extension for Chrome, Edge or Firefox, and send them to your coding agent. Free in beta for your whole team.