Most Jira tickets about a website start life somewhere else: an email with a screenshot, a Slack message, a comment in a shared doc. Someone then rebuilds them in Jira by hand, and the detail a developer actually needs — which page, which browser, what the console said — gets lost on the way.
PinReview connects straight to Jira. A reviewer pins a comment on the live page, and a Jira issue appears in your project with everything attached. Here's how to set it up and what lands in the issue.
What ends up in the Jira issue
Each piece of feedback becomes one Jira issue:
- Summary — the task title the reviewer wrote
- Description — their comment, followed by the page URL, severity, who reported it, browser and viewport size
- Console errors — any JavaScript errors captured on the page, in a code block
- Screenshot — uploaded as an attachment, with the pin drawn on it, and linked in the description
- A link back — "View #42 in PinReview", which opens the task with its full history and comments
PinReview files the issue as a Bug if your project has that type, and as a Task otherwise. On the PinReview side, the task shows the Jira key — say WEB-128 — as a link, so anyone looking at the board can jump straight to the ticket.
Set it up in a few minutes
You'll need a Jira Cloud site and an Atlassian account that can create issues in the project you want to use.
1. Create an Atlassian API token
Go to your Atlassian account's Security settings and choose Create and manage API tokens → Create API token. Name it something you'll recognise, like "PinReview", and copy the token. Atlassian shows it only once.
2. Find your Jira site address
Open Jira in your browser and look at the address bar. Your site is the part that ends in .atlassian.net — for example acme.atlassian.net. You can paste the whole URL; PinReview trims it.
3. Connect
- In PinReview, open your project's Integrations and choose Jira.
- Enter your Jira site, the email you sign in to Atlassian with, and the API token. Click Continue.
- PinReview checks the details and lists your Jira projects. Pick the one feedback should go to.
- Leave Create a Jira issue automatically for every new piece of feedback ticked, or untick it to send tasks by hand. Click Connect Jira.
Click Test on the connected row any time to check the token still works. Integrations are included on PinReview's paid plans.
Automatic or one at a time
Automatic suits teams where every piece of feedback is real work — internal QA rounds, or a developer-led review where you trust the reporters. Each new pin becomes a Jira issue within seconds.
Manual suits client reviews. Clients leave plenty of feedback that is a question, a duplicate or a "nice to have". With automatic creation off, the team triages on the PinReview board first, then opens a task and uses Send to… → Jira for the items that should become tickets. Our guide to triaging website bugs on a Kanban board covers that routine.
You can connect more than one Jira project to the same PinReview project — for example, front-end bugs to WEB and content fixes to CONTENT — and choose per task where it goes.
Things to get right
Pick a project with simple required fields. If your Jira project makes a field mandatory that PinReview doesn't fill — a component, a custom "customer" field — Jira refuses the issue. The error shows on the integration as Last error, with Jira's own message. Relax the field, or use a project without it.
Use a service account if you can. Issues are created as the account whose token you used. A shared "PinReview" Atlassian user makes it obvious in Jira where an issue came from, and the integration keeps working when a team member leaves.
Decide where status lives. The connection is one-way: PinReview creates the issue, and closing it in Jira doesn't move the task in PinReview. Most teams let developers work in Jira and move the PinReview task to done during the weekly review, so the client sees their feedback handled.
Keep the conversation where the reporter can see it. Clients can't see your Jira comments. Questions for the reporter belong on the PinReview task.
If it doesn't work
- "Couldn't find a Jira site" — check the address ends in
.atlassian.net. Only Jira Cloud is supported, not self-hosted Jira Server or Data Center. - "Jira rejected the credentials" — the email and token don't match, or the token was revoked. Create a new token and reconnect.
- "Jira refused: the token is missing a permission" — the account can sign in but can't create issues in that project. Check its project role.
The bottom line
Connecting Jira takes an API token and a project pick. After that, website feedback arrives in Jira as a complete issue — screenshot, page, browser, console errors and a link back — instead of a screenshot someone has to explain.
Using a different tracker? The same setup works for ClickUp, Linear and GitHub Issues. For Trello or Asana, use webhooks and Zapier.