Treatment of product suggestions

MJ. Smith

In the new forums, the suggestion forum has the same issue that it had in UserVoice and FeedBear - making a suggestion is as satisfying as dropping a stone into a black hole … there is no feedback which results in meaningless votes and expectations.

• please mark the requests for features that already exist so that users find the solution rather than waste time and votes on useless requests
• please merge duplicate requests so we can see something more representative of the actual support
• please mark the remaining requests so that we can distinguish (1) request that are on the level of bug fixes that may be done whenever you are in the code for other reasons (2) requests that are sufficiently complex as to require prioritization in the project plans for the next year or so … so we understand what has priority over them and (3) requests that are major reworkings of the code that require corporate prioritizing of a new code base … that we request so you understand our needs rather than expecting to see results soon.

Marking the requests like this would offer proof that Logos was actually listening to the requests and generate more realistic expectations with the users. If I were running the "project", I would try to have each release contain one change of the level "request that are on the level of bug fixes that may be done whenever you are in the code for other reasons." I would do this as a PR step, reassuring users that they were being heard and their requests addressed in the confines of resources and overall product plans.