Alternatives
Products that do what SnagRelay does
Collect User Feedback. Send It Straight to Your Tracker.
- 1RI
2011 · repoplay.com
- 2
- 3
- 4
- 5
- 6
- 7
- 8AF
Hi HN, my team and I have been working on a new tool to improve how bugs are reported to engineers. I used to be a developer, and I thought it was ridiculous the little amount of bug repro details I would get in JIRA tickets. Then I became a product manager, and I realized how time consuming and tedious it was to write good tickets for developers (and then understood why most tickets lack enough detail!) That’s why my team and I decided to build a browser extension for anyone to create bug reports that auto-include: console logs, network requests, session replay, timestamp, url, browser, OS…
2022 · jam.dev
- 9
- 10
- 11BS
Hey everyone! Every reviewer loves smaller pull requests, but they can be hard to do practically. We created a Github integration that adds the following features - Commit checkpoints (i.e. stacked reviews) - Autogenerated tabs (based on dependency graphs) - A central pull request inbox (highlights which PRs need your attention) Commit checkpoints helps authors stack smaller changes within a single pull request without having to manage tons of branch offshoots. It works by using the common “[x/n]” prefix notation (where x is the stack number). This is the workflow: - Author makes some…
2023 · backprop.io
- 12
- 13
- 14
- 15WV
Hi HN, I'm the CEO at https://replay.io. We've been working on time travel debugging for web development for a while (https://news.ycombinator.com/item?id=28539247) and more recently an AI app builder that uses that debugger to get past problems instead of spinning in circles (https://news.ycombinator.com/item?id=43258585). We've gotten to where we can pretty easily build apps to replace business-critical SaaS tools, some of which we're now using internally: * We built our own issue tracker to keep track of all our development projects, tickets, bug…
Dec 2025
- 16
- 17
- 18
- 19
Helping Agents and Human Orchesterators read the same notes.
Mar 2026
- 20
- 21
- 22PT
I've been trying to figure out how long feature development takes, for years. I'm not a fan of (a priori) estimations of work, which just seem like the wrong measure. I think I've got a better way. Genuinely interested if some git gurus can improve this. Particularly around the pre-push hook, which is dependent on retained squash commit text. Or if there's an entirely better way to achieve the same thing.
2025 · doocot.sh
- 23TY
2011 · hulkort.herokuapp.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →