devtrackers.gg
[deleted]
External link →[deleted]
External link →You guys are right that it hasn’t been getting updated as often as it should lately. Several months ago I took on more responsibilities and haven’t had as much time to devote to investigating bugs as I used to. The silver lining is that I’ve trained another person on how to add bugs to the tracker, and today will be training 3 more. You should see the list grow significantly this week, and going forward it should be back to getting updated weekly (if not more often).
Shouldn't the list of known issues get smaller?
edit: /s
It tends to cycle: old issues get fixed, new content gets introduced which comes with its own shiny new bugs. In the ideal world of unicorns and rainbows, we'd ship everything bug-free, but the reality is that as the code changes it breaks in new and interesting ways.
Out of curiosity, I seem to recall a post that made it seem like the known issue tracker was a side project that you had worked on outside of your normal ANET responsibilities--was this the case?
Or were other people involved in it and you were just the most visible one updating it?
Both are true, sort of. I'm making use of the work of lots of people by pulling these bugs from our internal database. We have a bunch of folks who find them (by testing, reviewing in-game reports, investigating reports in Support tickets, and combing the forums and Reddit) and enter them into that database. Then someone (formerly just me, going forward me or one of the people I'm training) chooses the most commonly reported and game-breaking bugs, flags them for inclusion, and updates the tracker. There is also some leg work to screen out things like bugs on unreleased content, weird technical stuff that would make no sense to players, and bugs that could be exploited.
Because the tracker lives on the Support site, I'm ostensibly in charge of it and I've been the one visibly talking to the community about it. But the work is a big team effort.
The community is doing some of that work for you, the wiki lists over 1000 bugs and counting by now: https://wiki.guildwars2.com/wiki/Category:Bugs (once you click an article, scroll down to the notes section. Bug is there.)
Especially in all those cases where a skill description says something different (for example different amount of damage) than what the ability actually does the wiki is especially helpful.
It may be worth anet's time to go through that list of bugs, since most of these are just minor things, like some text being off, and should be trivial to fix - but it will lessen the confusion/frustration about some things massively.
Plus (I know you can't really be expected to do that), it would be super awesome if you would edit the bug section out of each article when you're done.
I didn't know about that wiki feature, that's awesome! I definitely don't have time to comb through these right now, but I'll put it on the radar of our QA team so they can have a look. Thanks!
I'm curious, why no Automation around the Known Issues Tracker pulling issues/bugs from the database?
Also, do you really have a team that manually goes through and enters the bugs/issues into the database or are you simplifying the description?
I.E. Our team uses Gitlab's Issue Tracker to enter and track Puppet code bugs/features/enhancements/etc and soon I will be working with our ServiceNow admin to utilize the API for both Systems to allow our general users to create requests and reports in ServiceNow that are then auto-generated within Gitlab for our Team.
There's definitely some automation. The manual part is to determine what gets tagged for inclusion (filtering out the kinds of bugs I described above). Once something is tagged, it's status updates get automated. We still have to manually copy/paste the automatically updated stuff, but hopefully Soon(TM) when we update the Support site, we can automate that part, too.
Thanks for the info, and responding to my question! I had thought that something like this was the case: the work to find/review/investigate bugs being done by the team, but the outwards-facing Known Issue Tracker being aggregated by you (and soon to be others as well!).
It seemed that many people (OP included) weren't aware that the tracker was a side project on your own time to help communicate with the wider community, and that a lot of noise about 'broken promises' and 'they said so on the site' was being made by those who are wont to complain.
Case in point, the post below that stated
that [weekly] standard is not being maintained. We're just asking for them to abide by their own rules.
where your desire for weekly updates has somehow been transformed into a "rule" that the company has committed itself to--at least in the minds of the poster.
That being said, I'm sure it'll smooth over a lot of ruffled feathers if this project can be updated by a wider pool of ANet employees for more frequent updates. :)
Well, it's a fair criticism if we say we'll update it weekly and then we don't. When I first started this project, that was a reasonable target. Then I got busi(er) and transitioned the project over to someone else, and it was a reasonable target for him for a while, but then he got promoted and now also no longer has time. Hence training several more people this week.
While this did start out as a side project, after seeing the response and how helpful it's been for players, I'm not willing to let it die. Even if I don't have the time to do everything myself, I'll make sure someone gets it done.
And as discussed elsewhere, I still want to automate more of it. It's more automated now than it was at the beginning, but there's a lot more that can be done.
How do you handle Bugs that the Tracker claims to have fixed yet are not. The Known Issue Tracker stated that the Items: 20 Slot Pact bags are Soulbound on creation was Solved on 2016-06-13
I created one the next week and it is still soul bound.
Thanks for the heads up! It could be that it's by design, or it could be that we thought it was fixed and it isn't. I'll look into it and let you know.
Thanks, I was able to get a refund thru CS on it, I have sent you a PM with the ticket number
Ok cool, glad you got it sorted. I followed up on this and it turns out it was by design, so we removed it from the tracker because it's not actually a bug.