Feature requests
Browse public user pain points, feature requests, and delight moments detected from real reviews and communities.
Feature Request Tracking remains a workflow bottleneck
This signal shows that feature request tracking is being discussed through the lens of tool reliability and workflow flexibility, not as a standalone category. The evidence is thin and indirect, but it points to users evaluating whether their tracking setup can adapt to real workflows rather than just exist as a feature list.
Feature Request Tracking remains a workflow bottleneck
This signal captures a recurring friction in feature request tracking workflows: users are forced to build and rebuild their own tracking systems in general-purpose tools like Notion and Obsidian, and the underlying text editing and UI experience becomes the bottleneck. It matters because the pain is not about missing features but about the cost of maintaining a self-built workflow.
Feature Request Tracking remains a workflow bottleneck
Public feedback around 'feature request tracking' is really a story about scattered, tool-agnostic knowledge management: users praise Notion's flexibility but describe prototype and decision context living in docs, spreadsheets, and memory. The signal matters because the friction is not a missing tracker field but the absence of a single source of truth across teams.
Feature Request Tracking remains a workflow bottleneck
Users are actively seeking more efficient ways to track shipments and projects within Notion, indicating that feature request tracking remains a manual bottleneck despite Notion's flexibility.
Feature Request Tracking remains a workflow bottleneck
Public feedback indicates that feature request tracking tools are often over-engineered, leading users to prefer simple, incremental setups and to avoid complex workflows that create friction.
Feature Request Tracking remains a workflow bottleneck
Users are hitting a workflow bottleneck when trying to build structured, visually appealing dashboards for tracking feature requests in markdown-based tools like Obsidian, leading to frustration and tool-switching.
Feature Request Tracking remains a workflow bottleneck
Users are treating feature request tracking as a workflow bottleneck, often over-engineering tools like Notion instead of solving the core problem, indicating a need for simpler, purpose-built solutions.
Feature Request Tracking remains a workflow bottleneck
Users are signaling that feature request tracking tools become bottlenecks when they force rigid structures or lack native automation, leading to workarounds and maintenance overhead.
Feature Request Tracking remains a workflow bottleneck
Feature request tracking is fragmented across tools and memory, causing teams to lose context and spend meetings reconstructing decisions, which signals a need for centralized, AI-assisted tracking.
Feature Request Tracking remains a workflow bottleneck
Users are struggling with feature request tracking due to unclear handoff flows and information architecture, indicating a need for clearer workflows and better organization.
Feature Request Tracking remains a workflow bottleneck
The signal indicates that users value flexibility in unified workspaces but are hitting limits in specific feature areas, such as SQL query capacity, which can become a bottleneck for power users.
Feature Request Tracking remains a workflow bottleneck
Users are leveraging Notion's flexibility to manage feature request tracking, but the lack of a predefined structure forces them to design their own workflows, which can become a bottleneck.
Feature Request Tracking remains a workflow bottleneck
Recent public feedback indicates that feature request tracking is often handled through flexible tools like Notion, but users still struggle with capturing action items from meetings and integrating them into their workflow, suggesting a gap in automated tracking solutions.