Formal V11 Bug and Eagerly Wanted List
- This topic has 18 replies, 5 voices, and was last updated 3 years ago by
.
-
All right People ! Here is the V11 Wants & Bugs List.
A few rules please :
- Only put in bugs which have a most clear “bug” nature. Do not put in anything that is due to be worked out via the forum, or which only is a nuisance compared to V10.3. The shorter we keep the list, the more importantly it will be dealt with.
- Only put in bugs which have a most clear description in a separate topic in the forum. If the first post later appears to be not the most clear, but down the line it can be worked out for the better, you can refer to the post where it finally has been worked out (in that case link to the post and not to the topic ! see attachment under the mouse arrow for what to copy) . Don’t let PRT Development read for an hour before they understand the issue. They don’t have the time for that (and will hop to a next issue quickly).
Try to avoid more issues in one forum topic, but if it can’t be prevented, make two entries in the List and paste the same link in each entry. - Try to grasp the priority column in there. Please notice that others (like me) may change the priority. All are relative to each other. Issues which lose money can have Prio 1. Those unworkable because of unreasonable spent time, can also have Prio 1, maybe 2.
- The Wants actually don’t belong. However, they too can imply huge time loss if not solved. Look in there for the real examples (so far).
- Although everybody can edit the List, entries should not be changed for their content (like the description or the link) because that will not be noticed. Lines should most certainly not be deleted or emptied. You *are* allowed to change the Solved Y/N column, but only it the issue really has been solved. This actually should be stated / described in the originating topic, so that there can be no misunderstandings about it. N.b.: When you solve something via a backdoor solution, this may not apply to someone else. Or, is the backdoor solution is a solution just the same, the issue may be set as solved.
- Keep in mind that PRT Support and Development may be observing this same list continuously, from now on. See how they deal with it; understand how you may influence.
This very topic should not contain any (Wants or) Bugs. However, I feel that there has to be some communication possible over the content of the List. Preferably this is done in the topics of concern, but I think it will be unavoidable that we also discuss how to deal with the List, whether a certain additional Column possibly is required and so on.
When I myself see passing by an issue in the forum that was not obtained in the List but in my opinion should, I will add it to the List. Others are perfectly allowed to do this too, but I will scrutinize the justification to some degree (one goal : don’t overload PRT development). Regarding this, I just did the same with the original List which so gracefully was created by GraHal and which was so nicely provided with content by Kovit.
If you recognize the Bug or Want entry, please add your forum name in the rightmost column. This is not a must per se, but it could emphasize the importance of the issue.
I will add to the list myself too, which does not mean that I somehow have more rights to it. As a poster in the list I will be neutral. However, I have a long list under my hands already, which was never handed to PRT, so I may come across as profound; this is not intentional. I will soon start adding that list of my own, and you may use my issues as examples of the how and what, and what could be important or less (see Priority column). Also, as I am neutral, you can just as well debunk entries from me, which goes via the originating topics; is one of my own entries unjustified, this will be made clear in the topic of concern, and the issue will be set Solved.
As I have indicated elsewhere, I will be communicating the List to PRT Support, BUT for now anticipating that the communication eventually will go implicitly. Thus, hopefully we can some as far as that PRT 2nd line support or even PRT Development is looking into the List on a daily basis. If an issue somehow requires additional outlay, I will try to do that with my own 1st line support. But hopefully the description in the topic of concern speaks sufficiently.
If something needs to be changed in this first post of this topic, I would need to ask a moderator to do it. Thank you in advance !
1 user thanked author for this post.
Any progress on PRT using the V11 Wants & Bugs List. ?
Luckily I waited till today because at a last check this morning I found another 6 or so references to the V11 Bugs topic in general. Then I got distracted by work.
I am waiting till lunch time is over and then I am going to call.1 user thanked author for this post.
Maybe you can change the priorities (in Column G) to what PRT are currently working on then that would be a good compromise all round?
Yes, great idea. I still did not put it up to them in order to indeed make the best of it.
Btw and FYI : I was asked whether it “then also” would be all right if 2nd Line or Development would feed back directly to me. I obviously said Yes and what will be fed back I will put in the list or the topics themselves, or … maybe they do that themselves. I don’t know yet. Earlier this afternoon I was preparing a guiding email for them, but I again got lost in …
work 🙂So still good / better ideas to let this succeed ? … don’t hesitate ! Tomorrow morning it will be.
1 user thanked author for this post.
Dear people – The List (see first post) is now in PRT’s hands.
1 user thanked author for this post.
Find exclusive trading pro-tools on 
