Chris Gallagher
15 discussion posts
Web portal for up voting feature improvements, product roadmap, ability for community contributions?
Aug 24, 2020 (modified Aug 24, 2020)
•
#1
Thanks for the feedback on this! We don't currently have plans to make our feature request list and roadmap public, but if we do in the future, we'll be sure to let you know.
Thanks!
I understand why you would be hesitant to do this, but it is very frustrating to see features on the feature wait list for years. It feels a bit misleading to read you saying "I'll add this to the feature list" if the truth is that it is unlikely to be implemented for years or at all. Maybe some sort of compromise is possible? How about a list of requested features that you would like to add but are not on the next year's agenda and are not assigned to anyone actively working on them? Such as the ability to read/save/change Z-order for windows (for DisplayFusion)?
I can appreciate the frustration of not being able to see our roadmap, but I'd like to give some context as to how our feature request list works. It's a catch-all list for anything that's requested, so there are over 1000 feature requests on it, and we won't necessarily implement them all, but we like to track how many people are requesting them to help with our planning.
When we spec out a new version, we prioritize regressions from the previous version, as well as bugs that affect many customers. After putting those onto our roadmap, we then pick out a couple of highly requested features that we have the resources to implement and plan to add those.
Hopefully that gives some insight into our process, and why we can't really offer timelines on most requests, and also why some requests may be on the list for years. That being said, it looks like we are hoping to add the Window Position Profiles z-order stuff for the next major version (after 9.7.1), but don't hold me to it!
I see, that is useful context. If there are 1000 existing feature requests, then it won't do to list all of the things not currently planned. I'll suggest another compromise. If you aim to add 2 or 3 highly requested features for each release, how about making public a list of 10-20 (or some other number) of highly requested features that those 2-3 features are likely to be drawn from? At least users could have *some* sense then if a request they care a lot about has any chance of being added anytime soon, but does not obligate you to any sort of timeline and you do not have to make any commitment to eventual implementation of specific features.
