Add a "High Priority / Critical" bypass for the feature voting process
D
Derek Marshall
While the community voting system is great for general feature requests, it creates a major bottleneck for issues that have causes or critical bugs that impact daily operations.
When a system issue or broken workflow needs an immediate fix, we shouldn't have to wait for it to accumulate votes to get eyes on it. Please consider adding a way to flag high-priority, operational-impact items so they can bypass the standard voting process and be fast-tracked for a fix.
Shelby Parker
Thanks for sharing this perspective, Derek Marshall — totally hear you on how the voting flow can become a bottleneck when something is actively impacting day-to-day operations. This is really helpful context, and I’m looping it into our review with the team so we can assess options for a high-priority/critical flag or fast-track path. If you’re able to share an example of the kind of issue you’d want to escalate (and what “critical” means in your workflow), that would help us make sure we’re solving the right problem.