Page 2 of 3

Re: Tharros: Bug Tracker Operation I-2016

Posted: 23 Feb 2016 20:49
by Jiranthos
Hello!

Just wanted to ask a few questions about this operation.

How exactly can one from the outside help in this matter?

Seeing as I do not raid as much as I used to, or play all that much altogether - nonetheless - TW is really dear to me. The place of origin for many great friendships and memories. So I'd really like to help out, not really caring about any rewards at all.

I went on Mantis and checked the issues I had reported, logged PTR and tested them out again, since they were reported more than a month ago. Is there anything else I can do? Go through other (not reported by myself) reports and confirm them, test them? What else can a "mortal" really do?

Re: Tharros: Bug Tracker Operation I-2016

Posted: 23 Feb 2016 20:55
by Nyeriah
Well, there are several reports that were already fixed but are still stuck by the end pages of the tracker. Sure we managed to clear most of them, but there are probably more of them. If you already tested your own reports then you have already contributed more than most people do, as they usually report things and never again bother checking it :P

I think retesting these old issues is mostly hefty work, but eventually it's also a necessary work, basic maintenance. It's not something you'll dedicate a lot of time to, just try testing as many as you can or feel like. There are also the Feedback issues which require attention too at most times.

Also, checking the change log page frequently helps knowing whether there was a change applied to a given issue or not (these in general should be the ones that need retesting).

Re: Tharros: Bug Tracker Operation I-2016

Posted: 23 Feb 2016 20:56
by belekoxa
I'd suggest you to check the older ones and test it out if they are still buged. If a bug is still present in game, either comment it's confirmed, or better request an updater rank on bugtracker, so you can do it by yourself.

Re: Tharros: Bug Tracker Operation I-2016

Posted: 23 Feb 2016 22:33
by Jiranthos
Thanks for the info! I have an idea where to start now.

Just my final question: What does "feedback" status mean exactly? That the issue should be resolved, but hasn't been re-tested or needs more information about it post-fix before it can be closed/resolved?

Re: Tharros: Bug Tracker Operation I-2016

Posted: 23 Feb 2016 22:39
by gecko32
feedback can mean both of those.

Re: Tharros: Bug Tracker Operation I-2016

Posted: 23 Feb 2016 22:42
by Errorista
If its assigned to developer then its sign for me to test it after update, unassigned are usualy marked by me giving reporter 1 week (with some exceptions) to react or add some additional information, if you feel like staying tester for some time, you can help me with my TODO list.

Re: Tharros: Bug Tracker Operation I-2016

Posted: 23 Feb 2016 22:59
by Jiranthos
Errorista wrote: if you feel like staying tester for some time, you can help me with my TODO list.
Any help I can be, just point me at it. When I have windows of free time, I'll do as much as I can as often as I can. ;)

Re: Tharros: Bug Tracker Operation I-2016

Posted: 24 Feb 2016 12:56
by kurthos
Can you expand this event to PrimalWoW?

Re: Tharros: Bug Tracker Operation I-2016

Posted: 25 Feb 2016 03:20
by Nyeriah
I haven't seen the need of expanding this event to Primal because they only have access to a rather small scope of the project while TrueWoW has access to everything. Primal players wouldn't be able to contribute with much more than they already do.

Re: Tharros: Bug Tracker Operation I-2016

Posted: 25 Feb 2016 10:32
by kurthos
Nyeriah wrote:I haven't seen the need of expanding this event to Primal because they only have access to a rather small scope of the project while TrueWoW has access to everything. Primal players wouldn't be able to contribute with much more than they already do.
It would be cool to have a similar project for PrimalWoW to encourage more activity on the bugtracker. I think if you polled interest you would see many would be in favor.

Re: Tharros: Bug Tracker Operation I-2016

Posted: 27 Feb 2016 21:02
by Jiranthos
I went back to the first page of this thread and read the actual goal of the operation once more, in detail. It seems to be to reduce the count of Confirmed and Feedback issues. And with all the testing and reporting I have been doing over the past 3 or so days, I've increased the confirmed or new report count by something like 20, with surely more to come. It seems kind of ironic, that I would be working against the basic objective of the operation. :D
Just food for thought, no biggie.

Re: Tharros: Bug Tracker Operation I-2016

Posted: 27 Feb 2016 21:03
by Fastor
Ban

Re: Tharros: Bug Tracker Operation I-2016

Posted: 27 Feb 2016 21:32
by Nyeriah
TBF, I don't know :(

I had once as a personal goal to close 50 issues in a week, managed to close 32 or so. Next few days there were 80 new issues. So hmk. As I said in the main post, perhaps this is an impossible goal to reach, but the closest we get to it the better. So far we've had around 122 issues solved, so we were supposed to be at 600 confirmed reports but we are at 719 with 3 more months to go

Re: Tharros: Bug Tracker Operation I-2016

Posted: 27 Feb 2016 23:26
by Jiranthos
Many issues still haven't been reported on. That's the thing. If fixes continue and new bugs don't appear (or appear less in numbers than the ones fixed), at some point the reporting will slow down and the confirmed issue numbers will start to drop drastically. Don't get discouraged by the issue numbers growing. You guys are doing a terrific job and I don't know about others, but I really have noticed a steady progress overall.

Also,
Fastor wrote:Ban
Pls no.

Re: Tharros: Bug Tracker Operation I-2016

Posted: 06 Mar 2016 20:22
by Nyeriah
Operation Balance


[table][th]Week[/th][th]Feedback Issues[/th][th]Confirmed Issues[/th][th]Resolved Issues[/th]
[tr][td]---[/td][td]7[/td][td]729[/td][td]1045[/td][/tr]
[tr][td]#1 (Update 35 - 21.01.2016)[/td][td]25 (+ 18)[/td][td]712 (-17)[/td][td]1054 (+ 9)[/td][/tr]
[tr][td]#2 (Update 36 - 28.01.2016)[/td][td]10 (- 15)[/td][td]677 (-35)[/td][td]1105 (+ 51)[/td][/tr]
[tr][td]#3 (Update 37 - 03.02.2016)[/td][td]N/A[/td][td]N/A[/td][td]N/A[/td][/tr]
[tr][td]#4 (Update 38 - 10.02.2016)[/td][td]10[/td][td]675 (-2)[/td][td]1147 (+ 42)[/td][/tr]
[tr][td]#5 (Update 39 - 17.02.2016)[/td][td]8 (- 2)[/td][td]704 (+ 29)[/td][td]1172 (+ 25)[/td][/tr]
[tr][td]#6 (Update 40 - 24.02.2016)[/td][td]23 (+ 15)[/td][td]715 (+ 11)[/td][td]1212 (+ 40)[/td][/tr]
[tr][td]#7 (Update 41 - 02.03.2016)[/td][td]21 (- 2)[/td][td]723 (+ 8)[/td][td]1279 (+ 67)[/td][/tr]
[tr][td]#8 (Update 42 - 09.03.2016)[/td][td]N/A[/td][td]N/A[/td][td]N/A[/td][/tr]
[tr][td]#9 (Update 43 - 16.03.2016)[/td][td]8 (- 13)[/td][td]744 (+ 21)[/td][td]1328 (+ 49)[/td][/tr]
[tr][td]#10 (Update 44 - 22.03.2016)[/td][td]13 (+ 5)[/td][td]775 (+ 31)[/td][td]1342 (+ 14)[/td][/tr]
[tr][td]#11 (Update 45 - 29.03.2016)[/td][td]13[/td][td]780 (+ 5)[/td][td]1351 (+ 9)[/td][/tr]
[tr][td]#12 Update 53 (16.06.2016)[/td][td]18 (+ 5)[/td][td]801 (+ 21)[/td][td]1791 (+ 440)[/td][/tr][/table]