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.

[Bizmanager Pro] Implement Repair Ticket Workflow with Intake Form and Status Management

Implement a complete repair ticket lifecycle, including an intake form for creating new tickets, an auto-incrementing ticket numbering system, a finite state machine (FSM) for status transitions (e.g., RECEIVED, DIAGNOSING, IN_REPAIR), and API endpoints for creating, updating status, and assigning tickets.

Original Source

@@ramsesndame237 | 0 pts | 16d ago

## Goal Complete repair ticket lifecycle from intake to retrieval. ## Ticket Numbering Format: `REP-2026-001` (auto-incremented per year) ## Status Workflow (FSM) ``` RECEIVED → DIAGNOSING → QUOTE_PENDING → QUOTE_ACCEPTED → IN_REPAIR → READY → RETRIEVED → QUOTE_REJECTED → ABANDONED ``` ## API Endpoints - [ ] `POST /repairs` — create repair ticket (intake) - [ ] `PUT /repairs/:id/status` — transition to next status (validated transitions only) - [ ] `POST /repairs/:id/assign` — assign technician - [ ] `POST /repairs/:id/quote` — create repair quote from ticket - [ ] `GET /repairs` — list with filters (status, tech, client, date) - [ ] `GET /repairs/:id` — full repair detail ## Device Information (JSON) ```json { "brand": "Samsung", "model": "Galaxy S21", "imei": "...", "serialNumber": "...", "accessories": ["chargeur", "coque"] } ``` ## Frontend - [ ] Repair intake form with device info fields - [ ] Status transition buttons per allowed next status - [ ] Technicia

Discussion

Loading comments...