For me, this exchange was the writing on the wall.  I am talking to one of the forum mods about a critical bug in DS4 that prevented me from using it. (DS4 would crash withing 15 seconds of launch, with no user input required - just launching the program.)

Richard Haseltine - 12 June 2012 01:33 PM

a) bug reports are acted on, but many are duplicates and so aren’t marked as resolved.

b) it depends on the bug. Some are intermittent, or affect only a limited number of users, or appear only in special circumstances; for those reports are needed to identify the bug’s cause so it can be fixed. Other issues with the store - such as the lack of warning when repurchasing a previously purchased item - are known and don’t really need more reports.

If something isn’t marked as a new issue it’s probably worth a report, or a note to a pre-existing report if there is one.

 

ssgbryan - 12 June 2012 02:15 PM

Has ANYONE at DAZ worked in a production environment?  How on earth do you know what has been fixed and what hasn’t if you don’t update the tracker?  When I go into bugtracker & I see over 300 bugs (crashes only) that haven’t been addressed in months, how am I supposed to know if DAZ has looked at or fixed ANYTHING.

 

Richard Haseltine - 12 June 2012 02:28 PM

To an extent you won’t - though the Change Log for the app you are using should give some idea, if full or public betas are being released |(in fact for DS4 at least the change logs are in the wiki even for purely internal builds).

ssgbryan Posted: 12 June 2012 02:35 PM

OMG…..

I have worked places were we fired an entire IT staff because they had no idea what was fixed and what wasn’t.

Richard, does anyone at DAZ not understand that the person that turns in a bug will check back on a regular, if not daily basis to see if the bug has been addressed?  Does anyone not understand the messege this sends to the customer?

Now I know why I had to PM the CTO on a bug issue.

 

After this, I knew that I wouldn't be spending much time or money at DAZ anymore.....