RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Standup Bot] Improve integration with Jira for time tracking

Users are facing issues with their Product Owner misusing story points in Jira by comparing them to actual hours worked. A feature that better integrates time tracking with story points could help clarify this misunderstanding and improve the estimation process.

Original Source

@u/Rich-Brief6310 | 40 pts | 3/12/2026

I’ve been a Scrum Master for a remote agency for about 8 months. Our tech stack is pretty standard: Jira for ticketing, Slack for async, and Monitask running in the background strictly for our external client invoicing (we bill clients hourly). The problem is my Product Owner. He has fundamentally misunderstood what a Story Point is. Instead of treating points as a measure of effort and complexity, he is actively cross-referencing our Jira boards with the background hourly trackers. If a dev finishes an 8-point story but only logged 10 hours of active time on their timesheet that week, the PO confronts them in retro and asks why the point estimation was inflated. He is literally trying to find a mathematical conversion rate of 1 Story Point = X Hours. It is completely destroying our estimation process. The devs are now terrified during sprint planning and are starting to artificially pad their time trackers just so the PO doesn't yell at them for over-estimating complexity. I have explained to him five different times that points are abstract and time is literal, and they shouldn't be compared. He just points to the client budget and says, ""we need to know how much a point costs."" Has anyone successfully dealt with management weaponizing capacity tools against agile estimations? How do I get this guy to stop treating Jira like a payroll system?

Discussion

Loading comments...