Forum Discussion
Counting in the list of feature requests, you only have to go through the top 30 before the number of Kudos drops below 10.
In those top 30,
11 are selected for development
3 are implemented
6 are open for discussion
11 are new
Looks to me like the list is already being worked on "seriously". If an idea can't get at least 10 Kudos, then it's probably not worth the development time to add it.
Hi,
The "Feature Request Section" is not so popular among society members. So 10-Kudos achievement can take years... I believe that new feature implementation should be based not only on kudos count.
- mgroen27 years agoSuper Contributor
baxatob wrote:Hi,
The "Feature Request Section" is not so popular among society members. So 10-Kudos achievement can take years... I believe that new feature implementation should be based not only on kudos count.
baxatob I agree 100%.
There should be a more active approach to society members to let this become a success.
Also, some feature requests may have 0-1-2 kudos but are relatively easy to build/implement, while others with more kudos are not that easy (eg require a complete redesign). But working on the low valued kudos (with 0, or only 1, 2 kudos) might get to result that the product becomes much better!
All in all I do not see the kudo voting thing, resulting in improvements of the product to be very effective: when I look at the last few TestComplete releases compared to the implemented feature requests, there is no clear relationship between those.
- shankar_r7 years agoCommunity Hero
There are lot of features are related to workspace editor and debug which are very effective when it comes to scripting.
Most of us all working with scripts, IDE would be better with the feature available in the requests.
I too agree with baxatob and mgroen2, Kudos doesn't play good role in feature requests, It will not return effectiveness of the feature requests from Smartbear product users.
I'm much awaited to see some major and useful requests added into TestComplete soon.!!
- mgroen27 years agoSuper Contributor
baxatob wrote:Hi,
The "Feature Request Section" is not so popular among society members. So 10-Kudos achievement can take years... I believe that new feature implementation should be based not only on kudos count.
Should feature requests being done by paid users weigh more, compared feature requests done by trial users?
What do you think?
- AlexKaras7 years agoChampion Level 3
> Should feature requests being done by paid users weigh more, compared feature requests done by trial users?
I am not sure that this is something that can be implemented easily... (without considering any other aspects)
The main case here is that it is quite common when licenses are purchased on behalf of some executive who never either using the tool or have a need to visit a forum. While purchased licenses are used by employees who register and visit forum.
- mgroen27 years agoSuper Contributor
AlexKaras wrote:> Should feature requests being done by paid users weigh more, compared feature requests done by trial users?
I am not sure that this is something that can be implemented easily... (without considering any other aspects)
The main case here is that it is quite common when licenses are purchased on behalf of some executive who never either using the tool or have a need to visit a forum. While purchased licenses are used by employees who register and visit forum.
A suggestion to implement this could be: use the field Customer ID (as when creating a new support ticket), in feature request input field. At creation time it can be checked if the Customer ID entered is from a client which has an active license.
Like this:
Related Content
- 7 months agoFelecia628
- 10 months agoAnonymous
Recent Discussions
- 5 hours agoSubhraDas