How to Get the Development Team to Add Your Feature

Increase the chances of your feature request being implemented! Having screenshots and a walk-through of a step-by-step workflow is always helpful in determining next possible steps by our team. 


We are looking to meet our customers feature request needs. The QuoteWerks Development Team wants to add all of your requested features, but needs as much relevant information about the feature that you can give. The development team always needs real world needs and situation examples, rather than just an abstract feature request.


Feature request submissions need to have all the elements below:

  1. What are you trying to accomplish?
  2. What feature do you think you need?
  3. What is the real world need and/or situation you are in where you need this solution?


When describing a feature or area in QuoteWerks we need specific landmarks, like “on X window, when I press Y button” or a real-world example like "On the Purchase Orders tab of the Purchasing window, right click and choose Close PO."


If the development team has to guess what you mean, or go back and forth with questions and answers spanning days, the opportunity to understand the feature request and implement it will be lost, we will have moved on to something else.


The old saying "a picture is worth a thousand words" holds true. We really prefer that you always include a screenshot with your submission and edit it to mark it up to include annotations to call out the areas you are referring to.




3 people like this