Bug Tracker, Maraudon PTR & new horizon

[Mesh 48]

Dear community,

 

First of all, we would like to apologize for the downtime of the website last week. It was linked to the setup of the new bug tracker as we needed to upgrade some packages and that didn’t go as planned.

 

Bug Tracker

Finally, the bug tracker is now up and running, awaiting your reports right there!

Unfortunately, the old issues will require a resubmission and the old bug tracker will be only accessible by developers.

 

From now on, here is the new issue lifecycle with statuses:

• New: automatic status for a new submitted issue. The next steps is for the QA team.


• Need sources: if the author of the bug report did not provide valid sources that can confirm the authenticity of the issue.


• Invalid: the bug report is not valid and a comment from a QA team member will explain why.


• Duplicate: the issue has already been reported. You will find a comment linking to the main issue to contribute.


• Confirmed: the issue has been validated by the QA team and is now in the hands of the developers. From this stage on, the community can upvote based on the severity of the issue. 


• WIP: A developer was assigned to this issue, and it is being worked on.


• Test fix: a fix has been applied on the Developer Test Realm and QA team needs to test it. From that, the bug will either go back to WIP or advance to…


• Resolved: the fix is working and ready to be launched on live realm.

 

The search engine works with keywords, labels, milestones and statuses. It does not take into account the score of an issue.

 

We hope this new streamlined process will make fixing the important issues a more efficient task, that reflects what the community thinks is important to get fixed.

 

Maraudon PTR

The PTR is now ready for testing Maraudon with a special setting. Characters created are instantly level 48 and spawn near the entrance of the instance.

You will find special NPCs for:

Gear

Reagents

Class Trainers

Quests (all quests are turnable the NPC who gives you the quests)

 

Some special commands are available:

• .maxskill: command to max your weapon skills.


• .revive: to revive yourself or your companions. You can use commands in guild channel if you are dead e.g. /g .revive. This command is available to make testing more efficient, if abuses are affecting the feedback quality, it will be removed without warning.

We are interested in feedback regarding:

• Artificial Intelligence of monsters,


• Quests,


• Monster’s speeches,


• Spells and mechanics.

 

Change of horizon

Starting tonight, Unstop will be stepping down from the Community Manager position to move to the Quality Assurance team as a Senior QA. We hope this change of role will fit him best in the team! The role of Community manager will remain vacant for the foreseeable future.

[Summer 26]

I don't like the fact that I can't access the old bug-tracker anymore. I put effort in some of the reports with good documentation and quite a lot of them aren't fixed at this point. I will not write new ones for the same issues since I would have to look again with waybackmachine for the same links, quotes and explanations for no reason. Furthermore, the old tracker contains a lot of information in general about classic wow gathered by multiple people. That knowledge should be accessable.

 

Besides, I think the new tracker is confusing. Is there no index or register and no subcategorys to browse in? Maybe I am getting old but it looks like someone who did way to many presentations in powerpoint designed this.

 

Is it nessecary to register anew or is the forum account synced with the tracker? Seems like I can't login.

[Shenna 1135]

@Summer The old bug tracker will be available in read-only format for approximately one month after migration, don't worry. 

[Mesh 48]

Hello Summer,

 

You need to create a new account on the bugtracker with dedicated credentials.

I do not really understand your comment on the navigation as the Valkyrie menu, Bug Tracker Index, Login and Register are on the same line at the top of the website.

 

The categories are now working as labels which provide a better flexibility to filter the issues you are interested in. For example, if you want to check all the issues related to quests, you would set the label as Quest (link). But now, if you want to check the issues related to mage quests, you just need to add the label Mage to the existing label Quest (link). You can then add a text or a status to filter more the remaining issues to find the one you want very fast which is way more efficient than the previous bug tracker.

[Renew 26]

i have a problem with the new bug tracker - it doesnt open for me (im from germany) chrome says: ERR_NAME_NOT_RESOLVED

 

from proxy or TOR it does work but ofc its not rly useable like that...

[zyaldir 118]

Can we make issues by russian language on new bugtracker?

[Summer 26]

The colorchange to grey/white is definatily an improvement. Also nice to hear the old trackers is visible again. I hope it will stay that way.

 

/edit: Would be nice if links to the database would be shown in the new tracker like in the old with a thumbnail.

Edited September 21, 2016 by Summer