We appreciate you taking the time to share your ideas with us! Every piece of feedback helps us understand how we can make our product better for you.
When you submit a request, it goes through a structured evaluation process. While we would love to build every great idea, we have to prioritize updates that provide the most value to our entire community.
How We Evaluate Requests
Our product team reviews every submission. We look at four primary factors when deciding what to build next:
Impact: How many users will benefit from this change? Does it solve a common "pain point"?
Alignment: Does this feature fit our long-term vision for the product?
Feasibility: What is the technical effort required? Are there security or performance implications?
Urgency: Is this a critical fix or a request that unblocks a significant number of users?
Understanding Status Labels
You can track the progress of your request by looking at its Status Label on the portal:
Status | What it means |
Under Review | Our team is currently investigating the idea and checking for technical feasibility. |
Planned | We've decided to build this! It is officially on our roadmap. |
In Progress | Our engineers are actively writing code and designing the feature. |
Completed | The feature has been released. Check the latest release notes! |
Closed | We’ve decided not to move forward with this at this time. (See below for why). |
Why some requests are "Closed"
If we mark a request as "Closed" or "Declined," it’s usually for one of the following reasons:
Workaround Available: There is already a way to achieve the result using existing features.
Niche Use Case: The request is too specific to one user’s workflow and might complicate the experience for others.
Out of Scope: The idea, while good, doesn't align with the core purpose of our software.
Note: Even if an idea is closed today, we keep it in our archive. If we see a surge in similar requests later, we may reopen the topic for discussion.