When is the Issue Tracker going to be looked at?
- Thread starter Ozric
- Start date
There are a few bugs posted in this thread, we'd all appreciate it if you, and anyone else helped confirm them.
Put their feet to the fire. Keep the stats coming. Software companies (that means game developers too) need to do a better job in managing incidents and addressing tickets. Many of us know how the sausage is made now, we've been in the workforce for 20 years and are mostly nerds. The warning signs during the migration to the new bug tracker were glaring and when the complaints came in about usage they were ignored as completely as the tickets that were stacking up not being addressed.
Please FD, fix your bug tracking. Its an operational embarrassment.
Please FD, fix your bug tracking. Its an operational embarrassment.
Last edited:
If you have a Frontier account, you've already been drafted.
I've long accepted that ED is in it's final form, with the possibility of added future bugs. The whole vote for bug fixes jig is clearly to make people feel like bug fixes could happen.
My Frontier account is bugged though. I can't change the password. Also this one is linked to my old PS4 account. I don't remember why my PC account could get setup. Maybe it did. It's all so confusing. Oh dear.
IMO the issue tracker is a joke. I'm not using it for the reason the OP mentioned. However, even if it would work properly I wouldn't use it because I don't believe FDev is fixing bugs by impact but rather by "easy of fix". Obviously fixing a typo is way easier than fixing networking issues but one of these two is not as impactful as the other.
EDIT: Even top voted issues that are really old and annoying on top (that are regarding very basic functionality, in this case application termination) are simply-not-fixed: https://issues.frontierstore.net/issue-detail/791
I take it as FDev is overwhelmed by the amount of bugs in their game and do not possess the ability to fix them in time, let alone understand them as important staff has already left the company. Hence I am not going to report any further bugs to not additionally overwhelm them.
EDIT: Even top voted issues that are really old and annoying on top (that are regarding very basic functionality, in this case application termination) are simply-not-fixed: https://issues.frontierstore.net/issue-detail/791
I take it as FDev is overwhelmed by the amount of bugs in their game and do not possess the ability to fix them in time, let alone understand them as important staff has already left the company. Hence I am not going to report any further bugs to not additionally overwhelm them.
Last edited:
The issue tracker perception might be a chicken / egg scenario. If they truly intended to fix bugs / raise the quality, then maintaining the issue tracker would be a valuable effort for frontier. QA coverage for free is literal manweeks / months for their qa team, it would be a tangible cost if they ever decided to do it themselves.
Yeah when the fixed stopped showing up in patch notes, using the issue tracker didn't have much clutch power..
Yeah when the fixed stopped showing up in patch notes, using the issue tracker didn't have much clutch power..
It is a bit frustrating. I reported that my FC was reporting that it was carrying 33k/25k a few months ago, and there's been zero indication of progress on the issue.
issues.frontierstore.net
If others who have experienced this issue could confirm it, that'd be nice. Right now I have to use transfer all, which is a bit frustrating when I don't actually want to transfer all.
webapp
issues.frontierstore.net
If others who have experienced this issue could confirm it, that'd be nice. Right now I have to use transfer all, which is a bit frustrating when I don't actually want to transfer all.
Equally I wouldn't want them to avoid fixing the easy bugs just because they're stuck on a tricky one. There's a whole bunch of "this bit of UI is misaligned" / "typo here" / "installation doesn't have a name on the nav panel" bugs which should be relatively easy fixes, and which should be the sort of thing which a new hire could be given to get them used to the structure of the code, data, build environments, etc. before they're ready to be given something complicated.
It's interesting to see how player priorities have ended up on the bugtracker, too:
Of the top 20 voted bugs:
- "can't play the game at all / major crashes or disconnects in normal play ": 1, 4, 7, 9, 17(ish)
- "niche gameplay is broken, contributing to it being niche": 2 (powerplay), 3 (AX), 5 (megaships), 13 (powerplay)
- "is this actually a bug? only FDev knows": 6
- "annoyances that have been around so long they've accumulated huge numbers of votes": 8, 16, 20
- "cosmetic issues": 10, 14
- "missing/badly-implemented features": 11, 12, 15, 18
- "VR bugs": 19
Perhaps we need an ...
.....Expedition Of Errors,
....an in-game organised tour of our least favourite typos, mistakes, bugs and irregularities?
Itinerary to be finalised by player submissions.
The first commander to the error site reports on the issue tracker, others on the expedition can then verify and confirm if appropriate.
A fun in-game event that just could lead to improvements or at least let us all revel in misery together.
Wonder if we would have the same itinerary next year?
(in all seriousness if any capable cmdr or group organised this, I would support it)
.....Expedition Of Errors,
....an in-game organised tour of our least favourite typos, mistakes, bugs and irregularities?
Itinerary to be finalised by player submissions.
The first commander to the error site reports on the issue tracker, others on the expedition can then verify and confirm if appropriate.
A fun in-game event that just could lead to improvements or at least let us all revel in misery together.
Wonder if we would have the same itinerary next year?
(in all seriousness if any capable cmdr or group organised this, I would support it)
Ozric
Volunteer Moderator
Interesting that the numbers of confirming, confirmed and acknowledged are different to what I seeHere some current numbers of the issue tracker
all nicely hidden behind a double check (this time it was cross roads and traffic lights)
Elite Dangerous, all versions, unfiltered: 12189 hits (or 1219 pages)
works like a charm...
- confirming: 2670
- confirmed: 103
- acknowledged: 99
- fixed: 256
- invalid: 891 (!)
- by design: 76
- expired: 4174 (!)
- duplicated: 868 (!)
Ozric
Volunteer Moderator
I just went to the main issue tracker page, logged in, scrolled down and selected Elite Dangerous. The total issues are the same, but I get
- confirming: 3462
- confirmed: 125
- acknowledged: 121
- fixed: 331
- invalid: 1393
- by design: 91
- expired: 5571
- duplicated: 1216
As I see it, Issue Tracker was a way for FD to appear as they're doing something to fix bugs, while in reality they've probably moved most of the staff to other (hopefully Odyssey related) tasks. They've made players do all the work in researching and prioritising bugs, introducing ways for some of them to "expire". I see it as just a smoke screen, hiding the fact that fixing bugs is not a priority for them. Maybe it will change with Odyssey reloease, but now using that tracker is a waste of time for me. I only vote for bugs other people submitted and made public here on forums not counting much on that achieving anything - searching whether bug I found was already submitted is a pain in the back I don't intend to suffer, not to mention submitting something that will be ignored and will "expire" later.
Ozric
Volunteer Moderator
No indeed. I just though we might have found another bug with the issue tracker
It's not much of a coincidence in my mind that the issue tracker was launched early 2019, before we officially knew that they'd moved the bulk of the team over to work on Odyssey.
And this is one of the main reasons why something needs to be done about it. The issue tracker is obviously not fit for purpose, it's obviously not been designed with reporting and organising in mind. Up till now this hasn't been an issue for Frontier, though it has for the players who have put in thousands of hours recording bugs dutifully as we are told to. But when Odyssey moves into Alpha, it will be a massive issue.
Someone said earlier in the thread that when they hear the CMs ask us to log an issue as "it will get looked at" they want to throw something at their screen. I feel very much the same way, I think it's just a slap in the face to dismiss us to the issue tracker when it's been proven for years to be inadequate and not used in the way it should be.
Each time I have raised this with the CMs over the last couple of years I have been told that it will be investigated. The previous three times it has come to nothing at all. I had thought that this time might be different with Arf's new enthusiasm for listening to responding to the communities concerns... But here we are over two months later and not a peep.
Unless the purpose is for me to completely dismiss it and not report bugs anymore.
To bring it back on track (in my arrogant opinion and more in line with what @Ozric intended if I get it right), is that it's all about that all of us ED players want ED and Odyssey by extension to be a smashing success since we love the game so much, and for that to happen, we need a more serious approach to bug squashing and reporting with prompt and visible feedback than an "issue tracker" that looks like a popularity contest and, at any rate, has absolutely not feedback which makes players, those who care and those who don't, ultimately not want to waste their time with using it.
I fully realize that the devs can't give us all we want when we want it (usually four days ago), but we need a feedback mechanism, something visible, instead of "we'll look into it" and then silence for years.
Feedback is a two way street. You can't improve without it, and you won't get it without acknowledgement, some sort of acknowledgement. I'd rather have "sorry, can't do it" than silence, because the former at least lets me know that somebody saw it.
And yes, that IS my field. It's not an easy one, and I've failed too, but at least I know how it works. I've been doing it for 13 years.
I fully realize that the devs can't give us all we want when we want it (usually four days ago), but we need a feedback mechanism, something visible, instead of "we'll look into it" and then silence for years.
Feedback is a two way street. You can't improve without it, and you won't get it without acknowledgement, some sort of acknowledgement. I'd rather have "sorry, can't do it" than silence, because the former at least lets me know that somebody saw it.
And yes, that IS my field. It's not an easy one, and I've failed too, but at least I know how it works. I've been doing it for 13 years.
Last edited: