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.
Marsha_R wrote: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.
Marsha_R I disagree - it seems that "Selected for Development" just means that the idea is in the Smartbear backlog for TestComplete - it doesn't indicate that it will ever be worked upon in the near future and in fact one of the comments on the second highest rated idea suggests that given the current architecture it cannot be implemented:
"According to our development team, the official status of the feature should be "Not in progress".
According to the product owner, the feature request would be a great enhancement but based on our current architecture we are unable to implement this yet. Therefore I do not have a definite answer on when name mapping will be refactored."
I have to agree with mgroen2 that not much progress is being made on the implementation of feature requests, especially those with the highest ratings which have been around for a long time. If they are not possible then they should not be marked as "Accepted for Development" as this is misleading. We used to get an update in the monthly newsletter on the number of feature requests submitted vs implemented. As I have mentioned before I think this should be brought back to give better visibility and a thorough triage of the current statuses undertaken.
- mgroen27 years agoSuper Contributor
nebsta wrote:
Marsha_R wrote: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 newLooks 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.
Marsha_R I disagree - it seems that "Selected for Development" just means that the idea is in the Smartbear backlog for TestComplete - it doesn't indicate that it will ever be worked upon in the near future and in fact one of the comments on the second highest rated idea suggests that given the current architecture it cannot be implemented:
"According to our development team, the official status of the feature should be "Not in progress".
According to the product owner, the feature request would be a great enhancement but based on our current architecture we are unable to implement this yet. Therefore I do not have a definite answer on when name mapping will be refactored."I have to agree with mgroen2 that not much progress is being made on the implementation of feature requests, especially those with the highest ratings which have been around for a long time. If they are not possible then they should not be marked as "Accepted for Development" as this is misleading. We used to get an update in the monthly newsletter on the number of feature requests submitted vs implemented. As I have mentioned before I think this should be brought back to give better visibility and a thorough triage of the current statuses undertaken.
Totally agree with nebsta. With the additional remark that amount of Kudos should not be the only factor. Some feature requests might have little or 0 kudos but might be very handy to the user who initiated it. Also it might become handy for other users as well but not yet realised (by them). Some users are more experienced than others you know. These feature requests might be very easy to implement, in the sense that it costs little development / test time. The quick wins, so to say.
- nebsta7 years agoContributor
Yes the Kudos should perhaps be weighed up against ease of implementation, although I don't agree that we should be prioritising free vs paid users differently - it sounds too complicated for potentially no gain.
Related Content
- 6 months agoFelecia628
- 10 months agoAnonymous
Recent Discussions
- 4 hours agosimonaferrara
- 13 hours agoSubhraDas
- 2 days agotramuntana