Just recently Directus implemented an automated process for feature requests.
It has been over 90 days , and this discussion has not received at least 15 votes from the community. This means that we don’t feel like there’s enough community interest to warrant further R&D into this topic at this time.
This request will now be closed to keep our discussions tidy. Please reach out if you have any questions!
And
This feature request has received over 15 votes from the community. This means we’ll move this feature request to the Under Review state!
The Core team will schedule a meeting to review this request as soon as possible. The discussion will then be approved or denied. You may or may not be invited to join this meeting with the core team.
If I understood correctly, this meta feature request has to do with a special “label/tag” that will be for the developing team so they can easily get a a “mostly wanted” feature request list.
Every feature request will still be available to all users no matter this “label/tag”…
Is this right @JonL?
The idea would be to auto close those feature requests that don’t pass the threshold of votes needed(e.g. 10, 15, 20 votes) in certain period of time(e.g 90, 180, 365 days).
They would still be searchable but you wouldn’t be able to add new replies to it and they would be auto tagged and the votes removed.
You could reference them in a new feature request of course if you think you can gather the interest of the community or the team. Additionally the idea would be to fill a feature request template where you can gather all the requirements and also reference those old closed topics
Because who cares about a feature request that got 15 votes in 2018, 10 in 2019, and 1 in 2023. If the 60% of those voters are not even Wappler users anymore. The current system is not representative of the current interest of current paying users.
Current clients are cheated by old votes from old clients.
Wappler team of course has their roadmap and can include their own Feature Requests and build stuff that makes sense for their business.
I thought of that, but some people cancel their subscription for one or two months and then come back. You would be removing votes from FRs that were created last month.
I think the main issue is keeping FRs fresh, the community engaged and adding to the conversation, and the content of the request to be inline with current tech and best practices.
That is how Directus solved it and it might need tweaking of course or even a different approach. I just proposed this one because I found it interesting.
Wappler team does not really define their features/road-map based on FR votes. So unless they have any plans to actually commit to and implelent FRs which have 5-10-15 votes within a specific time, this FR does not hold any value.
There is not a single 2023 request in this list sorted by votes. All are are super old and not implemented. And only one marked as done - which took about 1.5 years to implement.
Another thing that Directus gets right is to compile the most voted FRs for the month and send them in their monthly newsletter.
💡 Top feature requests
Here are the top five most popular feature requests from the last 30 days:
🔼 31 – M2A relation alternative UI
🔼 18 – RFC for magic sign-in link via email
🔼 9 – Semantic search
🔼 9 – Inline editor
🔼 8 – Option to auto delete file when related item is deleted from collection
(Of course, we have lots of awesome long-standing requests to check out as well, but we wanted to highlight new ones you might not have seen.)
So they get the deserved visibility among those that don’t usually browse the forum.
