JKO wrote:I always tought that items on a wishlist were nice to have but are no showstoppers, have low priority, are something for a new versionnumber.
A bug/flaw is something which has to be adressed direct/soon/within a certain time periode and have certainly a higher priority than a wish.
Well, the bug tracking system we use here at Steema allows you to label a ticket as a "Bug", a "Feature Request" or an "Enhancement". Done the difficulty to reach a consensus on the definition of these categories and, more than this, to reach a consensus on the interpretation if some issues fit more in a definition than the next, we prefer not to discriminate between these categories. So we prefer to pay more attention to the "Severity" level assigned to the items.
JKO wrote:Time frame and priority are two key factors in these kind of lists.
We understand some of you have important problems that demand immediate intervention, but without any doubt, you'll understand we also have to value other aspects such as the number of customers affected, if there is a workaround or not, the percentage of the component that is affected, the relation cost/benefit of the implementation,...
JKO wrote:Sometimes you give a number to these issues (like TV52016112) and in this case not.
In what case not? I'm not sure to find what I've missed.
JKO wrote:In short, how and where can a customor see:
1. if he reported a issue or Steema accepted the issue
2. how the issue is handled/categorised (high/low priority, is a wish, a bug, or something else)
3. within which time frame can he expect the issue be solved
1. We use to say something like "I've added it to the * list". And we sometimes give the ticket assigned so the customers can look for the item in the release notes to see if a release includes the demanded fix/feature.
2. The technician evaluates questions like the mentioned above (number of customers affected, if there is a workaround or not, the percentage of the component that is affected, the relation cost/benefit of the implementation,...) to decide the item Severity. Of course nothing is definitive and we are happy to revise it when demanded.
3. We don't use to tell exact dates for fixes. It depends on the factors above and also on the difficulty of the solution implementation. And also, we can't omit the possibility of unpredicted complications when trying to implement a solution.
JKO wrote:To get to the point, when will this issue be solved and when will my other issue regarding the legend ("I've added it to the wish list to be investigated for future releases (TV52016112).") be solved?
I've revised the items TV52016255, TA05016254 and TV52016112. The two first items already have a quite high severity. I've incremented it for the last too.
Don't hesitate to let us know if there's any other issue you are interested on knowing its status.