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.

[ERPNext] UOM Short Notation - Quick inline unit entry without switching UOM dropdown

Allow users to enter a short notation for the Unit of Measure (UOM) directly inline without having to switch the UOM dropdown. This would speed up data entry and reduce unit errors, especially when dealing with different units like Nos and Cartons.

Original Source

@@orey-aajaamu | 1 pts | 5d ago

**Is your feature request related to a problem? Please describe.** 1. Yes. We procure or manufacture in Nos as the base unit but we plan, think and communicate in Cartons. This mismatch causes constant friction during data entry across Sales Orders, Purchase Orders, Stock Entries and Manufacturing entries. 2. To enter a Carton quantity you have to manually switch the UOM dropdown before entering qty an extra step that slows entry and gets skipped, causing unit errors. A sales person taking an order over the phone wants to type 5c and move on. Instead they have to click UOM field → select Carton → enter 5 → or remember to mentally convert and enter 20 in Nos(we sell in both as ctn and nos - so default we use nos). 3. Same problem when raising a Purchase Order or entering a Work Order, we naturally think "25 Cartons" but the field expects Nos and we have to do the math every time. This is not just a one-item problem. We have many items that come in different pack sizes - one item might

Discussion

Loading comments...