Can we get a “known issues” list please?

Reverb

After other big updates @ZOS_GinaBruno or @ZOS_JessicaFolsom will post a “known issues” list so we know which problems the devs are aware of without having to scroll through the Dev Tracker (which is littered with monetization posts).

There are some pretty big issues with the Blackwood release. Set bonuses not working, a block bug, companion gear going missing, non-functioning quests, and more. It’s been days now, Why no consolidated list of what’s known and being worked on, and how that work is being prioritized?

Instead of closing down threads that discuss these issues, recognize that the duplicative threads are a symptom of failing to communicate effectively about these issues, and address it.

Elsonso

If I had to guess... those lists take a long time to generate, and then follow up on. They are certainly handy. I would like to see them following every Update, but ZOS leans toward less public facing work like this, rather than more public facing work. Frankly, I am sort of getting tired of beating this drum since it never seems to do any good.

Reverb

Elsonso wrote: »

If I had to guess... those lists take a long time to generate, and then follow up on. They are certainly handy. I would like to see them following every Update, but ZOS leans toward less public facing work like this, rather than more public facing work. Frankly, I am sort of getting tired of beating this drum since it never seems to do any good.

We’ve seen the lists posted pretty quickly after updates in the past, but it’s always been sporadic if it gets done or not. It’s not that time consuming when you’re told to prioritize time on that.

How many times over the years has Zeni told us that the commit to improving communication? When it comes down to it though, it’s something they’re willing to say but not something they’re willing to consistently prioritize.

Nastassiya

The lists are not hard to generate. At my work, we have a Jira board specifically for defects. That can easily be exported but the problem is there will be people, on this forums, that will question every little thing the devs do and prioritize. Also, there will be vulnerabilities listed in that which players should not know about. Just for that reason I think there is no point to posting a defect list for the public to see. Defect lists should never be made public.

Starlight_Whisper

Let's start block bug - ongoing
Normal new trial dropping perfect - fixed
Normal new trial dropping overland gear - ongoing
Suger skulls UI bug - ongoing

Celephantsylvius_Bornasfinmo

- Block Bug in raids
- VMOL you have to recast your pets as a sorcerer or they just sit in a corner the whole fight
- PvP Performance post patch...
- I have had complaints that some people crash or get UI errors if a companion is brought out whilst in group

Elsonso

Nastassiya wrote: »

The lists are not hard to generate. At my work, we have a Jira board specifically for defects. That can easily be exported but the problem is there will be people, on this forums, that will question every little thing the devs do and prioritize. Also, there will be vulnerabilities listed in that which players should not know about. Just for that reason I think there is no point to posting a defect list for the public to see. Defect lists should never be made public.

Defects reported in the community are what I would expect to see in this list, not every little thing that they are working on. Part of the problem is that ZOS seems reluctant to tell people what is going on with reported problems, but people are equally unwilling to just wander off and let ZOS do whatever ZOS does when ZOS feels like doing it. True, they should, but they don't. Things fester. Threads get longer. And longer. Forum mods start pulling out the heavy artillery. ZOS gets accused of unnatural acts against nature, and other bad things. ZOS remains silent (wisely, at this point). People take silence as confirmation that ZOS is clueless about what they are doing, or worse, being deliberately antagonistic.

All around, a positive and heartwarming situation, it is not.

Edit: Meanwhile, when ZOS informs people, information is out there. No guessing. No "white knights" blindly defending, or angry mobs blindly hating. People may argue, or even disbelieve, but many will accept the situation when they know what is going on.

Fennwitty

It would cut down a lot of questions, and undoubtedly a lot of people were unaware there was anything going on at all with companion gear disappearing. They spent boatloads of money kitting out companions but no notice was given "hey, hold off equipping your companions guys we have a fix going in tomorrow" or anything of the sort from ZoS.

Celephantsylvius_Bornasfinmo

Fennwitty wrote: »

It would cut down a lot of questions, and undoubtedly a lot of people were unaware there was anything going on at all with companion gear disappearing. They spent boatloads of money kitting out companions but no notice was given "hey, hold off equipping your companions guys we have a fix going in tomorrow" or anything of the sort from ZoS.

Well otherwise people won't connect on the DLC release I suppose and that isn't good for them.

Nastassiya

Elsonso wrote: »

Defects reported in the community are what I would expect to see in this list, not every little thing that they are working on. Part of the problem is that ZOS seems reluctant to tell people what is going on with reported problems, but people are equally unwilling to just wander off and let ZOS do whatever ZOS does when ZOS feels like doing it. True, they should, but they don't. Things fester. Threads get longer. And longer. Forum mods start pulling out the heavy artillery. ZOS gets accused of unnatural acts against nature, and other bad things. ZOS remains silent (wisely, at this point). People take silence as confirmation that ZOS is clueless about what they are doing, or worse, being deliberately antagonistic.

All around, a positive and heartwarming situation, it is not.

Edit: Meanwhile, when ZOS informs people, information is out there. No guessing. No "white knights" blindly defending, or angry mobs blindly hating. People may argue, or even disbelieve, but many will accept the situation when they know what is going on.

They said they were investigating the shield block and companions. The companions gear issue has been allegedly fixed. With any product there will be a long list of problems and as long as they get worked on then it should be fine. There is no obligation to produce a massive lists of defects. It's like Googles Project Zero team that researches vulnerabilities in other companies products. Everyone always asks Google to not publish it and Google says "sure, you have 30 days!" No, you don't public defects lists period. If you accidently publish something, which can compromise security, by accident then you can crush a product.

Do you really want them to accidently publish a backdoor that was found? Oh, SHA1 was used by mistake. What about that gold dupe or SunSpire clipping issue? There is an extended delay with SYN-ACK with the Grayhost cluster. CyberArk isn't responding to requests from listed hosts. No, none of these are real, that I know of. Still, people do NOT need to know what defect list Bethesda has just to satisfy your curiosity. Just report the bug you found and go back to playing.

Elsonso

Fennwitty wrote: »

It would cut down a lot of questions, and undoubtedly a lot of people were unaware there was anything going on at all with companion gear disappearing. They spent boatloads of money kitting out companions but no notice was given "hey, hold off equipping your companions guys we have a fix going in tomorrow" or anything of the sort from ZoS.

Yup. Part of what this would resolve is hunting down statements that ZOS has made that are buried in some thread somewhere. Yeah, there is a [Z] in front, but that is usually ZOS_ConnorG reminding us not to bait people. Yeah, there is Dev Stalker, but that also includes press announcements, articles, and other stuff. The bottom line is that It is easy to miss things from ZOS, even in the thread where people are talking about it.

But like I said waaaay up at the top... I am sort of getting tired of beating this drum since it never seems to do any good. ¯\_(ツ)_/¯

Fennwitty

Nastassiya wrote: »

The lists are not hard to generate. At my work, we have a Jira board specifically for defects. That can easily be exported but the problem is there will be people, on this forums, that will question every little thing the devs do and prioritize. Also, there will be vulnerabilities listed in that which players should not know about. Just for that reason I think there is no point to posting a defect list for the public to see. Defect lists should never be made public.

Nobody's asking them to publish a list of their known vulnerabilities. Obviously they should curate what information is shared.

But "We've received reports of an issue affecting block cost and are looking into it" is not going to expose anyone's personal information or give them a backdoor to the server.

It lets us know that they're aware of things a lot of people are complaining about, and lets people experiencing problems not wonder if they're alone.

ADarklore

Well, we can keep the 'Companions losing gear' on the list since the patch this morning did NOT fix it.

Nastassiya

Fennwitty wrote: »

Nobody's asking them to publish a list of their known vulnerabilities. Obviously they should curate what information is shared.

But "We've received reports of an issue affecting block cost and are looking into it" is not going to expose anyone's personal information or give them a backdoor to the server.

It lets us know that they're aware of things a lot of people are complaining about, and lets people experiencing problems not wonder if they're alone.

That is exactly what the bug reports forums section is for. My company has Kanban issues, in our backlog, several months old. There are other things, which are more important, that keep coming up. Just because there is a list doesn't mean it's being worked on so seeing a list is pointless and it leaves risk of someone accidently publishing something that needs to be kept out of public view.

Fennwitty

Nastassiya wrote: »

Fennwitty wrote: »

Nobody's asking them to publish a list of their known vulnerabilities. Obviously they should curate what information is shared.

But "We've received reports of an issue affecting block cost and are looking into it" is not going to expose anyone's personal information or give them a backdoor to the server.

It lets us know that they're aware of things a lot of people are complaining about, and lets people experiencing problems not wonder if they're alone.

That is exactly what the bug reports forums section is for. My company has Kanban issues, in our backlog, several months old. There are other things, which are more important, that keep coming up. Just because there is a list doesn't mean it's being worked on so seeing a list is pointless and it leaves risk of someone accidently publishing something that needs to be kept out of public view.

So if a customer stops you in the hall and says, "Hey what about that bug I submitted two weeks ago?"

Is the appropriate response to pretend you didn't hear them and keep walking?

Elsonso

Fennwitty wrote: »

Nastassiya wrote: »

Fennwitty wrote: »

Nobody's asking them to publish a list of their known vulnerabilities. Obviously they should curate what information is shared.

But "We've received reports of an issue affecting block cost and are looking into it" is not going to expose anyone's personal information or give them a backdoor to the server.

It lets us know that they're aware of things a lot of people are complaining about, and lets people experiencing problems not wonder if they're alone.

That is exactly what the bug reports forums section is for. My company has Kanban issues, in our backlog, several months old. There are other things, which are more important, that keep coming up. Just because there is a list doesn't mean it's being worked on so seeing a list is pointless and it leaves risk of someone accidently publishing something that needs to be kept out of public view.

So if a customer stops you in the hall and says, "Hey what about that bug I submitted two weeks ago?"

Is the appropriate response to pretend you didn't hear them and keep walking?

Of course not! You duck out of sight before the customer sees you. Sheesh. Noobs.

Crash427

Elsonso wrote: »

Fennwitty wrote: »

Nastassiya wrote: »

Fennwitty wrote: »

Nobody's asking them to publish a list of their known vulnerabilities. Obviously they should curate what information is shared.

But "We've received reports of an issue affecting block cost and are looking into it" is not going to expose anyone's personal information or give them a backdoor to the server.

It lets us know that they're aware of things a lot of people are complaining about, and lets people experiencing problems not wonder if they're alone.

That is exactly what the bug reports forums section is for. My company has Kanban issues, in our backlog, several months old. There are other things, which are more important, that keep coming up. Just because there is a list doesn't mean it's being worked on so seeing a list is pointless and it leaves risk of someone accidently publishing something that needs to be kept out of public view.

So if a customer stops you in the hall and says, "Hey what about that bug I submitted two weeks ago?"

Is the appropriate response to pretend you didn't hear them and keep walking?

Of course not! You duck out of sight before the customer sees you. Sheesh. Noobs.

"You're hired!"
-ZoS, probably

Reverb

Nastassiya wrote: »

Fennwitty wrote: »

Nobody's asking them to publish a list of their known vulnerabilities. Obviously they should curate what information is shared.

But "We've received reports of an issue affecting block cost and are looking into it" is not going to expose anyone's personal information or give them a backdoor to the server.

It lets us know that they're aware of things a lot of people are complaining about, and lets people experiencing problems not wonder if they're alone.

That is exactly what the bug reports forums section is for. My company has Kanban issues, in our backlog, several months old. There are other things, which are more important, that keep coming up. Just because there is a list doesn't mean it's being worked on so seeing a list is pointless and it leaves risk of someone accidently publishing something that needs to be kept out of public view.

So you’d be ok with getting several more Kanban tickets every day because you haven’t acknowledged to your users that you’re aware of the problem? It sounds like you work for a company with poor support protocols and ITIL practices. Just because you are happy to hold Zeni to those same low standards doesn’t mean the rest of us should.

deleted221106-002999

Reverb wrote: »

After other big updates @ZOS_GinaBruno or @ZOS_JessicaFolsom will post a “known issues” list so we know which problems the devs are aware of without having to scroll through the Dev Tracker (which is littered with monetization posts).

There are some pretty big issues with the Blackwood release. Set bonuses not working, a block bug, companion gear going missing, non-functioning quests, and more. It’s been days now, Why no consolidated list of what’s known and being worked on, and how that work is being prioritized?

Instead of closing down threads that discuss these issues, recognize that the duplicative threads are a symptom of failing to communicate effectively about these issues, and address it.

I'd expect a list of "stuff that still works" would be shorter and easier to compile.

magnusthorek

At this rate, I'd be satisfied enough if the Community Managers simply talked to us. I mean, for real, no some sporadic 2-lines here and there or the Natch Potes AFTER updates