The Media Control Panel development is very active and we are constantly working to improve the software as well as implement features requested by our customers.
Our customers can voice their requests for new features and improvements through our customer feature request system.
Why should i use the feature request system? Can't you just record the feedback and implement my request?
Our feature request system is the primary source of truth for our business to identify what features and improvements our existing customers want. Submitting a feature request ensures that our wider team will get visibility of your request and that the request will never get "lost".
We do kindly ask our customers to submit feature requests through our system so that our support helpdesk can focus on resolving issues.
Why does my feature request rely on voting? It is important and should just be standard.
There are currently over 100 approved requests and 40 in moderation on top of feedback received through other channels. This means that we have to carefully select each change to be implemented and our systems are our attempt at a fair request and implementation process for all customers. Read more about how features are considered for development below.
How can i get other customers interested in my request?
Each week we will post a feature request onto our Facebook Group to ensure wider exposure. We also encourage our customers to do the same, using our facebook group to build up support for your feature request is a great way to get traction on a request.
Where can I submit a bug report?
Bug reports should be submitted directly to our Support Helpdesk by a direct MediaCP customer. Our team will assess and investigate the report and should the issue be deemed a bug we will create an appropriate bug report and provide a rough estimate of completion.
It is possible that a report will be rejected as a bug and you may be referred to submit a feature or improvement request instead.
How are features considered for development?
New major features are scheduled and built into major version releases (2.12, 2.13, 2.14, etc) whereas minor improvements on existing features and bug-fixes are included in minor version releases (2.12.1, 2.12.2, etc).
Before work starts on the next major release our team will review all features submitted through our customer feature request system compared additionally with both our own internal feedback system and features required to achieve our business goals. There are a number of factors to consider when selecting the features to be implemented, firstly our team will aim to select only one mid to large feature for each major release in order to ensure a healthy major release cycle of approximately 3 months.
To determine which features will be included in the next major release, we refer to the following questions in order to score each feature:
- The popularity of the request with existing customers;
- The ability to bring additional sales from existing or new customers to the software;
- The complexity of the request and how much effort is required for implementation;
- Whether the request is in line with our business goals
