Please Fix Feedback.DayzGame.com

[mr_snipes 7]

There are some issues i have reported and i have to say i feel there are issues with reporting issues.

 

The bug-reports i had reported about game-crashes have not been reviewed- except for one some people upvoted.

Since i am able to reproduce the issue i'd have loved to update the message. But i cant. I can just add another comment to my thread (which the  developer will most likely not read) or i can open another thread. The thread will probably be ignored, because people already see that there is some thread that shows that the game crashes. But not the version.  This is where the "community-vote-bug-tracker" has one of its weak points. The most upvoted threads are general game-design-questions that have nothing to do with bugs (flashlights shining through walls / zombies running through doors etc)

 

- the search-function only has one option - most "upvotes" and "most downvotes" There are 300 pages with reports across all versions both for experimental and regular hive. If i search for a headline i stumble onto so many threads from so many versions that i do not know what is what.

There is another search-function which looks like SQL- database-access to a ticket-system. You can build your own search. I did not get it to work how i wanted it and after 30 minutes and got frustrated.

 

What i really miss is a set of predefined searches - for instance: most viewed issues from Experimental Build 0.45.1234 new acknowledged issues for experimental build new issues that need more logs / crashdumps issues known and fixed

I know this cannot be fixed with one person in a day. BUT you have to employ three persons to fight that mess and it will not get less. Me and a lot of other players would love to contribute to this game as the disclaimer tells us to. If the reports are unnoticed for months that is frustrating. In case you want to let the community vote for the most urgent threads : give the community a better overlook, please.

 

In my opinion this feedback-tracker should be improved or replaced.

 

[kichilron 8550]

I have not heard of any major issues with the Feedback Tracker, but I will make Accolyte aware of your issue, so that it will be reviewed.

[Accolyte 1727]

Hello there mr snipes,

 

first of all, thanks for your post. We really appreciate all feedback we can get and try to improve the FT so that it is easy to navigate for all of us.

 

We try to scan primarily for crashes on bi-daily basis, but it is true that we may have been preoccupied with higher priority issues for most of this week. In case you think we missed any reports, please, feel free to post them in here and I will have a look at them or have them looked at.

 

 

most viewed issues from Experimental Build 0.45.1234 new acknowledged issues for experimental build

 

The problem with that is that people would have to always enter the right version in the version field. Sadly, they usually don't.

 

 

issues that need more logs / crashdumps issues known and fixed

 

All three are easily done.

 

Set up your filter to search for status "need more info" and the keyword "crash". For known issues you can search for the "acknowledged" status. This will turn up all the issues that are currently known to our team and are being worked on. For fixed issue you can use the "Resolved" window on the main page, which lists the most recently fixed problems, or simply search for all the bugs with the "fixed" resolution. It's true that these get spammed a bit by people being unstuck, but it does work.

 

Is there any reason you don't find these filters satisfactory?

 

Also, please note that just because we don't immediately respond to issues, it does not mean that we don't read them. We read almost everything that is on the FT, but not every post requires a response and sometimes we don't have enough relevant information to share at that time.

 

Please feel free to throw more concerns at me should you have any.

[mr_snipes 7]

Thank you for replying

 

 

 

OK, here are the threads that are still in "new" starting from old to new

 

http://feedback.dayzgame.com/view.php?id=10234   (march)

http://feedback.dayzgame.com/view.php?id=10278

http://feedback.dayzgame.com/view.php?id=11982

http://feedback.dayzgame.com/view.php?id=12163

http://feedback.dayzgame.com/view.php?id=13010

 

As far as i get the functionality of your ticket-system they should at least be set to "aknowledged"

 

What should i do if an issue remains the same in a new version ? Should i open a duplicate with new crashdumps ?

I cannot change the game-version of my report. The only bug i have reported that is set to aknowledged is reprducible in the new version (http://feedback.dayzgame.com/view.php?id=12743)

 

 

If you want to get murphy's law (wrong game versions) down to an acceptable level i would add a dropdown-menü giving the option to choose the version.

If you update the values with the current release-number each new release it should be fine. And you can make sure only two release-version can be chosen.

Since every patch in stable / experimental will be deployed on server-side as well it does not make much sense that someone reports an old issue. The user cannot play it anymore.

 

If i post on the MSDN-forums for instance there is the chance to see weither a similar  thread has been submitted already. The Forum-Software checks for tags and due to the category (let's say the c++-Forums for VS 2013 for instance) it knows which release to check.   So - if i would have chosen  EXP build .46.45.64.84979.8.79819 from the dropdown it could list similar threads according to the chosen headline. 

Would the feedback-tracker have such (working properly) the post-spamming would probably be less, because people would just upvote what's already there.  Or maybe you could have a few working filters as presets in the serach-function. Users can still customize their own. But looking at all those buttons and settings is overwhelming for most users.

 

Another thing i miss is a more detailled list of known issues than the one you post on reddit/twitter/steam/forums.dayzgame

So that i can look at the "known issues " and see   "hey they do not need another log for the issue where the game crashes if i eat a screwdiver"

Or "hey they have this very rare issue where a cow flies very far if you shoot it, they need more info"

Otherwise i'll just spam it in and eventually get frustrated,  because the time i spent to create the report looks like wasted, because noone looks at it for months.

I know this is not professional software-testing the way the big companies do it with professional testers who abide all the rules - but i think good design of the tracker can help.

[Accolyte 1727]

Thank for the links. Will look at them tomorrow. Today is a bit crazy, sorry.

 

If an issue is marked as "Acknowledged", there is no need for you to do anything else as long as it remains in that state. This means we got all we needed to fix the problem. This can obviously take some time as some issues have a higher priority than others which means, that some of the issues will remain in the game even after a patch is released. We don't need to be notified about that, we know about it all too well. If we need you to do anything for us, we will ask for it ourselves in the issue.

 

I have been thinking about having a dropdown menu for version like you describe, but I am a bit worried about what's going to happen with versions in issues once the version they were reported on is no longer available in the dropdown menu. I will have to consult our web design guys, but I will definitely remember to do that. 

 

I'm not sure if the FT is able to display issues with a similar title as you're suggesting during the creation of issues, but will look into it.

 

There are some preset filters on the main page (such as the resolved tab). We plan to add a tab with "Acknowledged" bugs which would also serve as a list of currently known issues.

 

Many thanks for taking the time to write this!