What arrives
- Title. The feedback number, the client's comment and the page it's on.
- The client's words. Exactly as they wrote them, quoted.
- Page and reviewer. The page address and who sent it, with their email.
- Browser and screen. Browser, system and screen size, plus a count of any JavaScript errors on the page.
- Scope. In scope, out of scope with hours, or a question, once you've confirmed it.
- A link back. To the item in Scopepin, with the page snapshot, any screen recording, the replay and the console.
New issue in Jira
#14 The signup button is cut off on my phone. (/pricing/)
The signup button is cut off on my phone.
- Page
- northwindbakery.com/pricing/
- From
- Maya Patel
- Browser
- Safari on iOS
- Screen
- 390 × 844
Open in Scopepin for the snapshot
How it fits your workflow
Client feedback usually reaches Jira the slow way: someone reads an email, takes a screenshot, writes a issue and pastes in the details by hand. With Scopepin, the client pins the comment on the site, and the issue writes itself: a title, the client's words, the page, the browser and screen size, and a link back to the snapshot of what they saw.
A typical round looks like this. The client pins comments on the staging site. You triage them in Scopepin first: answer questions, close duplicates and flag anything outside the scope. Then you send the real fixes to Jira in one go from the list, or switch on auto-send so every new comment becomes a issue the moment it arrives. Developers keep working in Jira as usual, and the link in each issue opens the snapshot, any screen recording, the replay and the console.
Scopepin stays the client's side of the conversation. Reply to the client by email from the item, and mark it done when the fix ships, so their progress page moves to done. Status changes in Jira don't flow back yet, so close the item in Scopepin when you close the issue.
Jira issues are written in Jira's own rich text, so the client's quote, the details and the link render cleanly in the issue view, on Jira Cloud sites you can access with your Atlassian account.
Setup
Set it up in a couple of minutes
- 1
Connect Jira
The workspace owner opens Integrations in Scopepin, clicks Connect next to Jira and approves access in Jira.
- 2
Pick where each project's feedback goes
On each client project, choose the Jira project its feedback should land in.
- 3
Send by hand or automatically
Send an item from its page or a batch from the list, or switch on auto-send so every new comment becomes a issue as it arrives.
If something isn't working
- There's no Connect button for Jira
- Only the workspace owner can connect tools, on Pro and Agency. Teammates see which tools are connected but can't add them.
- The Jira project I want isn't in the list
- The list shows what the connected Jira account can reach. Check that account has access, or disconnect and connect again with one that does.
- Sending fails with an error
- Usually the connection lost access, for example after a password change or when an admin removed the app. Disconnect and connect Jira again from Integrations, then send the item again.
- New feedback isn't sent automatically
- Auto-send is set per project. Open the project's Settings and switch on "Send new feedback automatically" under the tool, after picking where it goes.
- Issues land with the wrong type
- New issues use Task if the project has it, otherwise Bug. Change the type in Jira, or add a Task type to the project.
Questions
Which plans include Jira?
Pro and Agency. Every plan can post to Slack.
Do my clients need a Jira account?
No. Clients only ever see the feedback button on the site. Jira is for your team.
Can different clients go to different places?
Yes. Each project picks its own destination, so every client's feedback lands where that client's work is tracked.
What if the same item is sent twice?
Scopepin keeps a link to every issue an item became, and shows it on the item, so you can see it was already sent.
Does it change anything in Jira besides adding issues?
No. It reads the list of places you can send to and creates new issues. It never edits or deletes anything.
Which issue type does it use?
Task if the project has it, otherwise Bug, otherwise the project's first type. You can change it in Jira after it arrives.
Other integrations
Client feedback, straight into Jira.
Start free with one project. Jira comes with Pro and Agency.