Hey, we were getting pretty heavily off-topic in the other thread, so I split this to here. Continuing the discussion from Customized Entity Views:
I would love to see a feature in Fibery itself that could enable taking public feedback directly!! But I think for now that’s a big ask.
I know from following ClickUp that Canny can also be quite messy, and needs maintenance. At most basic level it requires changing of status (accepted, in dev, etc.), which also happens here, at least sometimes, by changing titles. This is a reasonable way to do it in Discourse, although tags might be as good or better. Canny also has poorer search, and this may be partly what contributes to lots of duplicates and diffuse feature requests. The ClickUp feature board is hardly a model, e.g:
You’d think that search would surface some really meaty discussions around the future of ClickUp’s arbitrary data handling, wouldn’t you? Plenty of unvoted requests, overlapping requests, unclear requests, etc. and no way to filter/refine. And I can’t change the sort order either. The default view of the main page also doesn’t seem to allow changing sort. Canny is hardly ideal to me, or at the least it - like Discourse - is best when well managed.
If Fibery suddenly switched to it, I don’t think it would substantively address a majority of your concerns, with the possible exception of the desire for a clear indicator of an idea/feature’s “popularity”, because Canny does have the single vote-up button for the feature itself and not just the individual post. Discourse can have this too though, as you know. It’s an open question why Fibery team doesn’t want to implement it, maybe they have confidence in their existing approach, maybe they have some concerns about the triviality of “vote up” interactions (I’ve heard developers express this before), I don’t know.
I did just look and I do think that Fibery uses the official Discourse hosting, which at base level is $100/mo. If they’re using that package, they don’t have access to the “Topic Vote” plugin. It’s $300/mo to get access to that in the next package up! So they’d have to triple their hosting costs for the forum. It comes along with other benefits, of course, but I can understand them not thinking it’s worth it just for voting if that’s the case. But also looking at that page/plugin description I just realized it might not do exactly what you might want it to: users get a limited number of votes. If you could replenish that on say a monthly basis, it might actually solve some of the potential concerns with a voting-based system, but I’m not sure. Maybe I should test it, I have a self-hosted Discourse instance on Digital Ocean now…
Anyway, I do know that there are more tools that could be used in Discourse for good feature management out-of-the-box. Sub-categories or Tags would both help with the organization issue, for example. There is also really good thread merging and splitting (both occasionally used here!), among other things. Ultimately though they’re all just tools, and they require staff time to do the actual management. That, I think, is the main limiting factor. Which is why I raised the possibility of them onboarding mods from the user community. There are of course risks and challenges in that, so I don’t pretend it is trivial or a panacea, but it might help, and is worth considering. That or make it part of someone’s job to be sure to fully manage the forum content, if it seems worth the time and effort. We have to accept, though, that it may not, and this forum is only one source of feedback they get. They also have a lot from Intercom which is invisible and may take priority…