Difference between revisions of "How we handle Feature Requests"
(Created page with "<div class="docs-related-pages">How we handle Feature Requests | How we handle Bug Reports</div> This document explains how we manage feature requests for the WHMCS p...") |
(No difference)
|
Revision as of 11:52, 9 January 2016
This document explains how we manage feature requests for the WHMCS platform.
WHMCS is a powerful and feature rich product used by tens of thousands of companies, of varying sizes, all around the world. As a result, we receive lot's of feedback and suggestions from our customers.
With finite resources and a big product roadmap, we have to decide what we work on based on a combination of both the value it delivers and the number of users it benefits. Unfortunately this means sometimes we have to make tough decisions.
Making a Feature Request
- We welcome suggestions and requests via our feature requests tracker at http://requests.whmcs.com/
- Before creating a new feature request, please search the tracker to see if somebody else has already requested it
- If you find one, please show your support by adding your vote and a comment
- If you don't, please submit your request. Be as detailed as possible.
Tips for Submitting a Good Feature Request
- Say what the problem is you are trying to solve
- Explain why you need it
- Provide real world examples where possible
What does Under Consideration Mean?
All requests start life in this status. This is the information gathering stage where we're looking for users to discuss, refine and vote for features that matter the most to them. If you agree with a request and feel it would be beneficial to you, please show your support for it.
While we do not implement features based solely on their popularity, requests that get a lot of traction in our feature requests tracker do get reviewed by our team.
How we Handle Feature Requests
- Our feature request tracker allows other customers to vote to show their support for requests
- We regularly review feature requests and suggestions as part of our routine product planning
- Due to the volume of requests we receive, it is not always possible to respond to every request individually
- We try to keep users updated using the status indicators in the feature requests tracker
- It is not possible for us to provide ETAs for individual feature requests
Feature Request Status Definitions
Below is a list of all feature request statuses along with an explanation of what they mean.
| Status | Description |
| Under Consideration | All requests start life in this status. This is the information gathering stage where we're looking for users to discuss, refine and vote for features that matter the most to them. |
| Currently Declined | A request that is not in our immediate plans, but we welcome further discussions and votes. |
| Investigating | A request is moved to the investigating status when our team is looking into the feasability of a request. This is no guarantee of future inclusion. |
| Planned | Planned indicates that a request has been or is already part of our future product roadmap and plans. This is no guarantee of future inclusion. |
| In Progress | This indicates a request is currently being worked on by our team. |
| Completed | This indicates a request has been implemented and released. |
| Already Possible | When a request is believed to already be offered by the product. |
| Declined | A request that has been declined and is unlikely to be considered. |
We thank you for being a customer, and welcome you to submit your feedback and suggestions.