I have an awesome new feature idea (either functional or sensor-wise) for PRTG. What is the best way to request its implementation and make sure that it is not forgotten?
This article applies as of PRTG 22
Our approach to handling feature requests
In the past, we used a bang-for-the-buck method to handle feature requests and similar feedback by our customers, see How does Paessler Handle User Feedback and Feature Requests?. However, as customer requests are ever increasing and we still want to ensure that no request is lost, we thought of a new method.
Feature requests via the Knowledge Base
We decided to use our Knowledge Base as an interface for us, Paessler Technical Support and Development, and you, the PRTG users. This has several advantages:
- Supplying a feature request is easy.
- The status of the feature request is transparent.
- The list of feature requests can be maintained in a reliable manner.
If you would like to submit a feature request, take the following steps.
How can I submit a feature request?
- Search the current List of Feature Requests and check if a request for the feature you would like to have is already there. If yes, simply vote for it.
- If you are not able not find the feature, ask a new question.
- Enter a descriptive title for your request.
- To optimally describe your feature or idea for improvement, copy the following template, paste it, and fill it out to make sure it contains all necessary information. Otherwise, we and other PRTG users will have a hard time evaluating your request.
---- Want this feature implemented, too? Please **upvote** by clicking **Thumbs up**! (Posts as a reply won't be published in this feature request thread. [[https://kb.paessler.com/en/topic/79245|Read Me!]]) ---- ==== User story As a PRTG user, I want ... ==== Details of user story Enter the details of your request here. Make sure it's as detailed as possible, depending on the complexity. ==== Acceptance criteria * Criterion #1 * Criterion #2 This basically gives us a set of cornerstones that need to be there in order for the feature to be implemented. ==== Status Open
Make sure you tag your question with prtg-kbtracker AND one of the following tags:
|Tag||Use the tag if...|
|add-feature||... you would like to have a new feature in PRTG.|
|add-sensor||... you would like to have a new sensor, for example, for a new appliance.|
|improve-prtg||... you would like PRTG to be improved regarding a certain aspect, for example, regarding the usability of the PRTG web interface.|
Your request is now in the review process. The List of Feature Requests will then be updated and will include your request. And other PRTG users will be able to vote for it.
How do I vote for a feature?
If you want to have a feature request evaluated by us, vote for it by clicking the Thumbs Up button of the feature request article.
Important: Posts with +1 or I want that, too as a reply do not count and will not be published.
How can I keep track of the status of my request?
The original posts will automatically be updated with corresponding status messages that will be as descriptive as possible.
Are requests with many votes always implemented?
Such requests will definitely be reviewed. Eventually, we will have to see if we can implement requests in a feasible manner, and how much people power would be required for the implementation. If the feature is easy to implement and test, and has a high score, it will be implemented more likely. If the request includes an entirely new sensor, it may take longer for us to get this done. We will ultimately deny requests that are simply not feasible, however, we will give a detailed explanation in this case (that is, as detailed as possible).
Is there a PRTG roadmap?
Not every good idea will end up on our roadmap and our plans may also change while in progress. For example, because it turns out that a feature will work differently than we initially expected. We will only know this when we have an innovation that has been run in our labs.
But, as soon as we have something new, we would love to hand it out to you as soon as possible. That's why early releases of PRTG are available to all of our customers.
Why are there no replies in the feature request threads?
We will only publish status updates for the feature. User feedback is not published in order to keep the noise down and avoid dilution of the request.