How to submit a Feature Request.

Sorry, but the feedback mechanism is a one-way blackhole, at least from this side. Hiding feature requests behind feedback rather than being able to discuss them within the forum is not going to work.  A better way to handle feature requests is to enable voting and perhaps use an assigned upvote count to each person as at least some other feature request systems work (e.g., you get N votes to assign to features, you can vote more than once and you can move them around). This change is a step in the wrong direction.

Integration between Community & Product Board is on the roadmap for later this year.  We have a few technical constraints we need to work through, but we definitely hear you and once we get going we’ll have a feedback group here on Community. 

Love @mnagel’s suggestion on having feature requests in the forums so users can provide feedback, further improvement ideas, etc.  By giving customers a way to upvote requests from other customers you’ll be able to see where the common pain points are and where development focus should be.

In general, I’d probably say that “Feedback” and “Feature Request” communication channels should get separated.  An acceptable option would be providing a choice at Feedback creation:

“What is this feedback about?

• UI look & feel
• UI text, grammar, spelling error
• Product Feature Request”

In both cases, as a customer I very much want to be able to track the progress of any feedback or feature request that I might make and as noted above the current mechanism does not provide this; in fact b/c I don’t even get an ack or receipt I am pretty sure that I’ve submitted the same feedback multiple times.

So here’s hoping that the Feature Request pipeline (and the Feedback one too) is getting a makeover as part of this Community re-launch.

[ZBXNEXT-5878] Enhance permission checking/handling - ZABBIX SUPPORT

Above is an open source vendor taking feature requests… publicly sharing what requests have come in, voting by customers so you know it’s important to the user base.

They are sharing code changes, etc. which is TMI and not required but the concept is the best I have seen and it’s adopted by other enterprise vendors and keeps this open and honest about interests of the wider customer base.

Just a JIRA project with some minor customization and you can have something like above going and it’d improve the feedback experience tremendously IMHO.

Excellent!  Far better to have Feature Request discussions in the open, so we can all discuss / vote / contribute.

@David Bond @Cole McDonald  @Stuart Weenig as we are working through the process of Product engagement, Ideas and PB, please do not hesitate to tag me, or flag anything that needs immediate attention.

I may not know all the technical detail to respond, but I am happy work to get you answers!

Agreed it’s been a black hole in the past. Interested to see what changes are in store now that the new community is going live, and Product Board is supposed to be in use. The general opinion of most LM customers about feature requests is stated pretty well above by @mnagel. It’s a one-way black hole. We submit through the product and never see anything about it ever again. Posting to the community has been good to get qualification of the request, but in the last 10 years, posts in the feature requests category have gotten next to 0 attention from LM.

LM: Listen to your existing customers, not just the fish that’s not yet on the hook. Your existing customers are where your ARR comes from.

We need a Feature Request Revolution! ✊

I see that as the main reason to have switched community platforms.