LostS77 (DayZ) 15 Posted December 31, 2013 So I have been trying to follow the reports on the FeedBack site... and I am noticing you all close tickets without filling in what version a bug/feature was fixed/added to. So could you all please start filling in that? It would be really nice to see what issues you all have fixed in future patches. 3 Share this post Link to post Share on other sites
TheLastEmp 295 Posted December 31, 2013 Would be nice... and not very time consuming... Would appreciate! 3 Share this post Link to post Share on other sites
Heeeere's johnny! 69 Posted December 31, 2013 (edited) The thing is that the feedback tracker is already way overloaded with billions of tickets, reporting the same issue or some slight variation of it. I follow the tracker myself and when I recognize a ticket, reporting an issue which has been posted already, I politely encourage the ticket creator to close it and use the search function to check if an issue has already been posted, just as a lot of reporters are doing, too. If nobody provides me (good) arguments why not to do this, I'd continue and also recommend others to do the same, because the devs already have enough problems, sorting the important from the less important. And except for simply reporting stuff, I'd like to help a bit keeping the feedback tracker just a tiny bit clearer. So, this is one explanation I can give for why so many tickets are closed without filling in when it has been fixed - because very often it's just a duplication or maybe the reporter accidently claimed something to be an issue, which actually wasn't one. I like to share arguments about my opinion so you're welcome to provide some and/or to critcize (constructively). :) Regards,Johnny Edited December 31, 2013 by Heeeere's Johnny 2 Share this post Link to post Share on other sites
LostS77 (DayZ) 15 Posted December 31, 2013 Johnny, Ohh I completely agree. Way to many duplicate ticket. I am starting to put down if something is a duplicate if I can. So yeah I high suggest doing what your doing. Just I know when a developer closes a ticket saying "fixed in latest patch" that drives me nuts. I am always wondering, what was the lastest patch at that time... Cause the issue could have come back :( So yeah... Billy 2 Share this post Link to post Share on other sites
Heeeere's johnny! 69 Posted December 31, 2013 (edited) Just I know when a developer closes a ticket saying "fixed in latest patch" that drives me nuts. I am always wondering, what was the lastest patch at that time... Cause the issue could have come back :( Oh, now I get what you mean! So now, I totally agree with you. ^_^ I definitely support this plea. As "reporters", we are encouraged to fill in the correct version as well (and will allways do). And it's happened here and there that a bug, however, came back with a later update. So yeah, dear devs, please do NOT use phrases like "fixed in latest patch" - Instead, please use something like "fixed in patch 113925". We will really appreciate it! :) Regards,Johnny Edited December 31, 2013 by Heeeere's Johnny 3 Share this post Link to post Share on other sites
Atomizer 53 Posted December 31, 2013 This thread deserves my beans, beans for all! 2 Share this post Link to post Share on other sites
TheLastEmp 295 Posted December 31, 2013 Good stuff. Bumped for increased viewing. 1 Share this post Link to post Share on other sites
Publik 404 Posted December 31, 2013 I definitely support this plea. As "reporters", we are encouraged to fill in the correct version as well (and will allways do).I tried entering 0.30.XXXXXX (first 0.30 patch, don't care to look for the number) and it told me the version was invalid, so I had to put in 1.0... Share this post Link to post Share on other sites
Heeeere's johnny! 69 Posted January 1, 2014 Yeah, I tried 0.30.XXXXXX too, but as it didn't work, I simply removed the dots, so now I do 030XXXXXX. Would be better, if there was a template of how they actually want it. 2 Share this post Link to post Share on other sites
