You’ve a mix of several subjects. It is recommended to have a topic per question. It may make sense to group topically correlated questions in a single topic. It makes less sense to use a common topic for different questions which are topically less correlated. You mixed the question on a specific feature request for CHD with questions on feature requests, questions on formal processes, and questions on roadmap. So a split into four subjects might have been more adequate.
As you’re still at a low level of community participation, it is expected less that you know all the details already. If you would be relatively new to our community, the same applies to expectations. You joined our community more than a year before me. And I still don’t know how to create an article in our community.
Yes, there is a product roadmap. At the start page of the community support section , you’ll find several resources linked. This includes
and various other helpful resources. There exist more web pages where you may find links to some of those resources.
The product roadmap is outdated and neglected. One view reports that it is 11 months old. The content date of redaction claims that it becomes two years old by end of coming week. Reality is that the main part is almost two years old while a few small parts might be half a year younger or such 11 months old. Although it is outdated, it is neither void nor became it reduced to a historic page. You may consider yearly topics about the plans of Spiceworks for the following half year or remainder of year as a supplement. Such supplements started mid-May 2021 and continued in September 2022 . It is not sufficient to read the original post of these subjects. The comments are complementary.
Yes and No. Yes, there is some formal process for submission of feature requests. No, such formal process is not documented. So you may question how a process might be formal if it is not documented. I consider such a question as reasonable and don’t have an answer to it. It uses a web form for submission . Mandatory parts are not identified. If mandatory parts are missing, you’ll get corresponding warnings or error messages. And there exist complementary statements of Spiceworkers which you may consider as dispersed elements of documentation. Several Spiceheads, including me, are spreading and repeating such information. And here is the feature request section for Spiceworks Cloud Help Desk (CHD) .
Similarly, there doesn’t exist a formal documentation neither of the feature request section nor of its processes.
- Do you feel a need for documentation of feature requests section?
- What are your questions for such documentation that you want to get answered there?
If I may find time to try writing some documentation in a how-to, I may learn how-to writing and eventually get learning also other forms of documentation. I prefer such a write up as team work with redaction opportunities. But it seems to be intended to get written only by a single author.
It is important to write feature requests, to vote on them and to comment them as Spiceworks uses their ranking AND the comments to determine priority of implementation.
So please create a feature request. Email template has been released only since mid August 2022. Your feature request will not be the first one on these email templates. It is helpful to also provide the reason, reasoning and use case in a feature request.
