Issue Tracker: unconfirmed issues expire after 30 days

CMDR MAIN SEQUENCE

CMDR MAIN SEQUENCE
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."

KS8xQL7.jpg


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.
 

Factabulous

Factabulous
Seems like the kind f thing they should have posted about ...

Edit: I think I approve, but at the moment I haven't been even looking at the issue tracker - because it's a trashfire. This also means we can never get non-mainstream bugs fixed as they will never get confirmed...
 

Vandaahl

Vandaahl
Rubbernuke said:
So in essence then FD only fix the bugs that annoy people, rather than severity.
Click to expand...
Well, isn't there a relation between the 2?
As in; game braking bugs affecting a high amount of people get a high severity, because otherwise it would result in a high amount of annoyed people?
 

Kenneth McGrew

Kenneth McGrew
CMDR MAIN SEQUENCE said:
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."

KS8xQL7.jpg


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.
Click to expand...
thats all a load of 🐂:poop: because the dolphin heat bug had over 33 CMDRs confirm it and yet it languished and is still live on the issue tracker as "confirming"

there is also this on the issue tracker showing how serious folk take it just to get bugs to to top of a chart......

BOUHC93.png


popularity contest for bugs... pfftt what a load of old rubbish....

oRWn-h.gif
 

Codger

Codger
For me the issue tracker is a huge fail. It seems to be designed to be confusing, and to make it difficult to tell if your issue is even in there already. And there is clearly nobody going through and merging reports anymore, like they used to.

It's a terrible system, with poor feedback and a horrid interface.

I guess you can tell I don't like it much. I think it's a big step backwards.
 

MickyG1982

M
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.
 
Last edited:

fu9ar

fu9ar
Cool so instead of brigading the forums you can brigade the issue tracker instead. This place should not be used as a bug tracker anyway!
 

Rubbernuke

Rubbernuke
Vandaahl said:
Well, isn't there a relation between the 2?
As in; game braking bugs affecting a high amount of people get a high severity, because otherwise it would result in a high amount of annoyed people?
Click to expand...

An example that shows the system does not work;

I found a feature breaking bug in Powerplay during the beta, reported it and FD never fixed it before release, even though it was real and blindingly obvious it was a problem. The report simply vanished five seconds after I posted it, drowned out by inane DSS requests.

FD need to sort out bugs that matter, and not just by how many votes it gets. The method here suggests to me FD can't fix everything and its running triage.
 
You must log in or register to reply here.
Back
Top Bottom