You must be logged in to access this page

Feature Request - Getting Started


1) First you need to Log into this QuoteWerks Forum website


If you have ever sent in a ticket to support, your login id is your email address.  If you don't remember setting up an account, simply click "Forgot Password" on the login screen and you'll be able to reset it.  You'll use the same login for tickets as you will for the forums.  


Once you are logged into the QuoteWerks Forum, you will have access to view, comment, and up-vote existing Feature Requests. You will also have the ability to post your own QuoteWerks Feature Requests in this forum.



2) How to Get the Development Team to Add Your Feature


The QuoteWerks Development Team wants to add all of your requested features, but 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?
    1. What feature do you think you need?
    2. What is the real world need and/or situation you are in where you need this solution?
    3. 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."
    4. 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.


If your request has all of the above, it will greatly increases your chances of your feature request being implemented


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.


Watch the video: https://www.quotewerks.com/support.asp?play=pGOXu8bfuu8


3) What do the Done, Waiting, Addressed and Partial topic prefixes mean?

 

There are hundreds of feature suggestions on the QuoteWerks Forums. 


When the QuoteWerks Development Team reviews your feature suggestions, they may add a prefix to your Topic Name. This is used by them to know that they have reviewed your suggestion and tells them to either read further if there was an update to it or skip it and move on to the next feature suggestion.


Done - Means the suggestion was thoroughly described by the people making the feature suggestion and Development has or will soon implement the suggestion


Waiting - This typically means that the Development Team asked a clarifying question and they are waiting on a response. After a period of inactivity, this topic prefix, may change to Addressed.


Addressed - This prefix means multiple things. This could mean that the development team asked a clarifying question and the response did not follow our guidelines for submitting a feature. It could also mean that we discussed the topic with you and decided that there was not anything else to do at this time. If you see a topic with an Addressed prefix and want to add something to the topic, it is best to create a new topic and include a link to the older topic. If the Development Team sees an Addressed Prefix, they will in most cases no longer review the topic.


Partial - Means that we have partially addressed or implemented one or more of the suggestions in the topic.


We value your product suggestions. The QuoteWerks Development Team needs thoroughly thought out suggestions with real world examples when you submit your suggestions.  Make sure you always follow the guidelines above.


9 people like this