6wingseraph is notable one and should just be kicked out.

This is ridiculous, we don't need 3 factor authentication for a downvote, its not that deep

You think serial downvoting is not a problem? Please explain why.

So serial downvoting by https://report.bistudio.com/members/556rifleman has now caused my profile to go into the negative. This really needs to stop.

I guess we can add https://report.bistudio.com/members/okonkwo to that list as well now.

@l909 Are you aware that serial downvoters are active on the BI trackers? What is the position of BI on this matter?

It doesn´t really change anything onno, a report or comment is judged by it´s merrit not some juvinile downvotes. it´s often the downvoters only imput on this forum as I´ve noticed they hardly ever report anything them selves... 😄

*merit

*juvenile

*input

*themselves

I have the most submitted issues of any user on the entire platform for the DayZ project specifically. Proof:

I would like you to explain yourself. It is still very juvenile behaviour, regardless of the number of issues you've reported.

We are looking into this. However, the ticket validity is not measured by upvotes and downvotes and will be processed regardless (this is not to downplay the issue but more about making sure that you are aware that we will still pay attention to the issues posted)

@dragino

It’s mostly the same few people doing this.
You could try restricting this functionality for them.

I'm not sure where on the Feedback Tracker terms and conditions, or dashboard, or anywhere else, that downvoting at will is prohibited. This is a non-issue that is receiving attention as an issue only because of an incredibly vocal minority. Upvoting certainly doesnt cause an outcry from users demanding written explanations for their upvotes, and serial upvoting happens just as often, where users upvote tickets that are of low quality so they might get a chance at attention or whatnot. I think that's equally bad or worse.

This ticket also begs the question: What is the function of upvotes and downvotes at all? It seems meaningless for a site focused on reporting and tracking user-generated feedback and bug reports. It's not a social media site or a forum. If I recall correctly, on the old Feedback Tracker, this functionality wasn't even possible.

One possible argument in favor of upvotes and downvotes might be, "well, it helps important issues get more visibility." For example, the Static Memory Issues ticket by @6wingseraph has over 200 upvotes at time of writing, and it certainly deserves attention. However, we have it from the BI staff themselves:

" ... ticket validity is not measured by upvotes and downvotes and will be processed regardless... " (https://report.bistudio.com/issues/FT-194?commentId=6ad4bff40a84f883660e1e21)

If this is true, then upvotes and downvotes truly have no bearing on how much attention a ticket receives. So, the "popular issues get more attention" argument goes out the window.

I see no reason for upvotes and downvotes to even exist. They add nothing to the site, and a user's Reputation score in terms of the upvotes and downvotes they've received has no bearing on the attention their tickets receive. All it does is add colorful banners to the user's profile if they receive certain numbers of upvotes. It seems this little bit of status is very important to some users.

I have been serially downvoted several times by several different users, who downvote close to my entire post history. It doesn't seem to matter or affect the attention my reported Issues receive. My profile has "gone into the negative" the same as @onno described above, yet my tickets still receive attention, comments, etc. It simply does not matter.

The feedback on upvotes/downvotes is important to us, and we will strike the best balance between giving upvotes/downvotes and their limitations so that no one can lose all of their karma points.

There could also be a cleaning process to identify suspicious downvotes, so expect your karma to return.

Thanks for sharing your thoughts!

To add some perspective on why the upvote/downvote system is such a major improvement: on the old tracker, users had no clean way to show that an issue affected them too, other than leaving repetitive "+1" comments or subscribing to the ticket.

This often cluttered the comment section with zero-value noise and made real discussion harder to follow.

The current voting system solves this completely. It gives the community a quick, zero-clutter way to signal issue priority and visibility to developers, while keeping the comment section focused strictly on constructive details, logs, and workarounds.

Thanks for sharing your thoughts as well.

I respectfully disagree for the following reasons: In the time I've spent on this tracker, I've found the signaling-issue-priority thing to be only partially true. Oftentimes the tickets that receive multiple upvotes, receive them because the title is all caps, and something like "CHEATER 4403 OFFICIAL PLEASE BAN!!" or something like that. While I don't have proof, I think it's plausible to imagine the following might happen every now and again: A 3 or 4 man team gets wiped by a hacker. One of them says "let's report this to BI, all you guys create accounts too and upvote it so it gets seen."

Well-documented, legitimate tickets often receive no votes or downvotes only, simply because I imagine their title isn't as eye-grabbing for the average user and doesn't generate a click, and you have to click on the first ticket to be able to vote. I'd link some examples but I'm on mobile right now. However you can look back at thr last few months of tickets on DayZ Stable and you'll see what I'm talking about with the titles.

You mentioned the old feedback tracker - on the old tracker, one thing I remember is you could tag the severity of an issue when creating a ticket. Major, minor, and a few more I think. Perhaps that could be re-implemented instead. I'm sure some might abuse it and just tag all their issues as super severe, but it seems more neat and practical rather than having each ticket accompanied by a voting value like a Reddit post.

I think the users that report issues often, would not abuse an issue severity tag. Many of us have a mix of reports - visual bugs, suggestions, cheater evidence, etc. All of these each deserve varying levels of priority and I think the user could determine that.

I can see how upvoting might signal issue priority in theory, but again we have it from the staff themselves that they're not using it that way: https://report.bistudio.com/issues/FT-194?commentId=6ad4bff40a84f883660e1e21

Screenshots from the old tracker ^

This was not re-introduced as large part of the userbase does not know how to prioritise issue correctly and we use our own internal priority system therefore the field was redundant - tickets would get attention regardless

shouldn´t be any voting on tickets tbf. got something to say just say it dont hide behind some downvote.