Usersnap is a visual bug tracking and feedback SaaS company, and its blog covers web development tools, SaaS, and remote team productivity.
HN commenters mostly mention Usersnap as a tool for collecting screenshot-based user feedback, including some from users and its CEO, rather than discussing the blog.
If you deploy on Vercel, the preview builds are automatic, and there is on-page commenting and discussions: https://vercel.com/docs/workflow-collaboration/comments
There are similar tools if you're not on Vercel, like https://usersnap.com/l/visual-feedback-tool
But beyond that, I don't think you should be having all the long discussions in the same place that you keep your tickets (let's say a kanban board). Have your discussions wherever you want, but keep them between the 2-3 people really involved. Then once they have an idea of what needs to change, THEN they can make a ticket for it with just some simple bullet points (linking back to the full discussion if they want).
Having everyone comment in the QA ticket directly mixes up discussion about the ticket itself and discussion about what to ticketize (which should've been done previously, outside the ticket). It's too much detail for the rest of the team to keep up with. They don't need the whole sordid history of how you got there, just what needs to be done.
In the teams I've been on, that previous discussion would happen all over the place... sometimes over Slack, sometimes over coffee at the coffee shop next door, sometimes in Figma/GDocs/Vercel comments, whatever. But once we come to an agreement, one of us writes the actual ticket without all the baggage, keeping it simple and clear.
----------
Edit: I think it really helps to have someone on the team who cares a lot about organization (and maybe even enjoys…
I currently use:
- Ghostery (https://www.ghostery.com/) - analysing cookies and installed trackers on a site
- Usersnap (https://usersnap.com) - for tracking bugs and collecting feedback for our website projects
- Pocket (https://getpocket.com) - bookmarking
- Zenmate (https://zenmate.com/) - for not worrying about country blocked content
- Image downloader (https://chrome.google.com/webstore/detail/image-downloader/cnpniohnfphhjihaiiggeabnkjhpaldj)
Hey this is really interesting. Congratulations. A few questions/observations.
1. You should really be linking to - https://usersnap.com/jira that website has a lot more clarity.
2. In your pricing page you mention '10 users'. What constitutes a user?
3. If I have three projects, how would I select a project from the screenshot?
My name is Florian, I'm one of the co-founders and CEO of https://usersnap.com
Since we're competitors, I won't add specific advice. However I'd like to encourage you to stay in business as I'm absolutely convinced that the market we're in is big enough and that the idea behind the products we're building is a great idea.
Yes! I still want to default to accept-language, but asking is key. What is your pattern for giving the user an option? I like this article in that it rejects icons, but I don’t like how they arrive at one language for multiple regions https://usersnap.com/blog/design-language-switch/
You're right - every user action / step is hard for support.
We tackled this problem with Usersnap (https://usersnap.com ) - devs will get accurate information (Browser + OS version and a screenshot) directly with the bug report!