RenewedVision has advanced software used by thousands of organizations, all around the world. That means we receive a lot of great feedback, suggestions and wishes from our customers of all shapes and sizes.
Unfortunately, this means we need to say 'no' a lot more than we would like. In fact, in many cases we are unable to provide a response or timeframe to each feature request. However, we do read all of the feedback and suggestions sent to us, and prioritize feature request based on a number of factors.
We want to be transparent about the way we handle feature requests, so have outlined how we handle feature requests below.
Feature requests in general
- You are invited to share your feedback and suggestions about feature requests in the feature requests sub-section of the community forums.
- We do not implement features based solely on their popularity - we take a number of factors into consideration.
- We do not provide ETAs for feature requests or publish long term roadmaps at this time.
Making a feature request
We regularly review feature requests and suggestions made on the forum. The forum is where suggestions start out, where they gather popularity and evolve as ideas.
- Before creating a new feature request, search the feature requests forum to see if someone else has requested it.
- If you find one, please show your support for an existing request (it is more likely to gain attention than if you post a duplicate one) by saying how you would use a feature rather than simply saying "me too!" or "+1" on the request.
- If you need to create a new feature request, create a new posting in the appropriate section.
Tracking feature requests
- When we decide to implement a feature request, we may log it in our development tracker.
- If a feature request has a number in front of it such as [#1234] that means it may make into a future update. This is not a guarantee.
- Remember that we do not publish long-term roadmaps. We have internal product roadmaps to plan our future releases.
What goes in, what stays out
We take into account a number of factors when deciding which feature requests to implement. This is a combination of feedback from our customers, people we consider power-users, our own market research, the availability of our own team and resources, and how the feature fits in with our long-term product plans and strategy.
Special thanks to Kayako for allowing us to borrow, nearly word-for-word, this article. Kayako is the help desk software we use for tickets and our knowledgebase.