Issue Tracker: unconfirmed issues expire after 30 days

[rootsrat]

Case in point: https://forums.frontier.co.uk/threa...hologram-cage-outside-of-the-fss-grid.525069/

I have reported that yesterday. The thread is on nearly 40 views now and nobody confirmed the issue on the tracker yet. But you can clearly see the bug in my screenshots. Now if FDEV will miss that one and won't "confirm" it on their side either, my effort to log it will be in vain. (Granted it wasn't that much of an effort, but still - I'm a customer, a player and I commit my time to this).

 

[sollisb]

Well, if folk would actually confirm on one rather than make up yet another entry that (I.e take up the effort to use the search function) it really wouldn't be a problem.

Unfortunately, in a lot of cases, 10+ people create a new entry, same 10+ people, each one has nobody else confirming it so none of them get confirmed and it gets deleted... the search function isn't really all that bad & definitely works.

It's not our job to search if someone else has reported an issue. that's Frontiers job, which, they have disingenuously-side-stepped, with this approach.

When I see a company doing things like this I immediately think, 1. They're only interested in the money, 2. They don't care about the consumer, and 3. They're a sub-par house.
Frontier have proven all 3 many times over. Basically, the Graphics and Sounds departments prop the rest up.

 

[Enderby]

Oh! Nice way to sweep issues under the carpet.

 

[DNA-Decay]

Was just looking at the Issue Tracker FAQ and noticed the following change that has quietly been introduced:

"If a certain number of players have been able to reproduce an issue within 30 days, the issue will become “Confirmed” – if the required number of reproductions is not met in this time, the report will expire."

A reminder that 10 confirmations (reproductions) are required to change the status to Confirmed (3 for FD's other games).

So if "only" 9 people add to a report, tough, the bug gets forgotten about.

And what about issues that have one or more duplicates* where each report has less than 10 confirmations but added together they have more than 10? Sure QA eventually get around to marking them as dupes, but do the confirmations in the dupe get added to the active report? (*which is itself a product of the poor search facility)

Interested to hear what other members of the community think about this.

I think we should be able to spend Arx promoting bugs.

200 Arx for a Tier 1 Helpdesk level investigation; 200,000 Arx for a patch next week.

 

[Rubbernuke]

Bugs fixing should be decided Mad Max style in CQC, the winner gets the fix.

TWO BUGS ENTER! THREE BUGS LEAVE....erm, thats not right.....

 

[Old Duck]

In the old days, Frontier would archive all bug reports with each update regardless of whether those bugs were fixed or not. I lost count of how many times I resubmitted the same bug over and over. Eventually I just said, "Screw it!" These days if a bug "bugs" me, I post it here in the main forum. That new Bug Tracker is a joke and a waste of time.

 

[Ian Doncaster]

In the old days, Frontier would archive all bug reports with each update regardless of whether those bugs were fixed or not. I lost count of how many times I resubmitted the same bug over and over. Eventually I just said, "Screw it!" These days if a bug "bugs" me, I post it here in the main forum. That new Bug Tracker is a joke and a waste of time.

Sure, but that archiving was to do with the forum being a silly way to do bug tracking more than anything else. I reported a bug in the 3.0 forums, had it archived as usual on the 3.1 release ... it was still mostly fixed in 3.2. The successor bug report for the stuff they broke while fixing that is still hanging around at "confirming" in the issue tracker, though, and will presumably expire soon.

I wouldn't object to them archiving on major version releases - looking through my "confirming" bugs, I think about half of them have either been fixed or have ended up with a "confirmed" bug reporting the same issue, so don't need to stick around - but 30 days is far too short, especially given the need for ten confirmations.

The only confirmed bug I have was on page 1 of the "top voted" bugs yesterday - but because it takes a minimum of 19 days to reproduce it, it took several months to accumulate enough confirmations to be votable, even without duplicates to dilute it. (It didn't help that half the people submitting "me too" comments weren't ticking the "can reproduce" checkbox, and so didn't count)

The bug I reported on engineer progress articles being messed up was put in in April. It stuck around in confirming for four months until the same bug affected Chloe Sedesi in the Enclave - at which point it got switched to Confirmed directly by Frontier and fixed within a day. If the confirmation threshold for Elite Dangerous was the 3 they use for their other games, then it would have been confirmed - and perhaps fixed - long before it became more visible in the Enclave.

 

[Gibbon]

This stinks of a 'get out of jail free card' from the devs. This way they don't have to fix anything really unless 10 people report it. Utterly shameful behaviour from any developer tbh, but something i've come to expect from FD.

 

[Unknown Zombie]

but 30 days is far too short, especially given the need for ten confirmations

The ten confirmations is wholly unnecessary in some cases. I've got two issues that I posed back in May, both of which contain videos of me reproducing the issue at will, that are still not confirmed. I have video proof of the bug! It exists! Come on!

 

[StevieG]

The only time a ticket should be closed is if fdev has requested further info and it was not supplied.

A logged ticket that supplies all the required information of the bug, to be closed by fdev and swept aside, is not the type of service I expected when I purchased the lifetime expansion pass.

 

[Starman 1966]

And even if a bug is confirmed 10 times within 30 days does that necessarily mean that FD cares about? No.

That is the courteous version of things that I would have preferably written instead.

 

[Autoculto]

It was always going to be a sneaky method to sweep problems under the carpet, so I can't understand why anyone is surprised by this.

 

[RevCaoticFox]

Was just looking at the Issue Tracker FAQ and noticed the following change that has quietly been introduced:

"If a certain number of players have been able to reproduce an issue within 30 days, the issue will become “Confirmed” – if the required number of reproductions is not met in this time, the report will expire."

A reminder that 10 confirmations (reproductions) are required to change the status to Confirmed (3 for FD's other games).

So if "only" 9 people add to a report, tough, the bug gets forgotten about.

And what about issues that have one or more duplicates* where each report has less than 10 confirmations but added together they have more than 10? Sure QA eventually get around to marking them as dupes, but do the confirmations in the dupe get added to the active report? (*which is itself a product of the poor search facility)

Interested to hear what other members of the community think about this.

this is FDEV forcing us to do THEIR JOB, and punishing us FOR NOT doing their job

 

[metatheurgist]

I can understand why it's being done, but 30 days is a ridiculously short amount of time to get 10 confirmations. One year might be more reasonable.