Sometimes I faced with bugs in game, for example missions descriptions/hints were wrong. I used an ingame bug-reporting tool (F12, report bug) a few weeks ago to report them. Bugs were not fixed, I don’t see them in “my activity” with other issues I raised. So I have a question: does in game bug reporting tool works? If I see no results - I’d say it doesn’t and I’d like to have a contact with DEVs from CCP to diagnose it (in exchange for PLEX/SP of course! 
1 Like
The ingame bug reporting works but the website that tracks bugs does not show any bugs or their status. this was discontinued years ago “temporarily” and never reinstated.
It’s pretty bad that we no longer can track the status of our bug reports ever since CCP removed that feature.
There’s no way to follow up on a bug now if you have additional info or clarifying answers.
Bug reporting feels like scribbling your issue on a paper and dumping the paper in the trash, hoping for it to end up in Reykjavik.
Zero feedback.
Please improve this, CCP.
2 Likes
There might be a way to give additional information for bug reports through Support Page, I think, if you provide them with the relevant BR-identifier (Bug Report) you can probably ask them to forward the information to the BR.
No guaranties though.
That’s pretty low priority, so when you say:
Are you expecting a low priority bug like mission text to be fixed within a few weeks? (That’s not sarcasm, that’s a sincere question.)
If you’re not a software developer, or you’ve no experience with Agile methodology (which, I’m only assuming CCP uses because seemingly everyone does), this is how development usually works:
- The user submits a bug.
- That bug goes into a bin somewhere.
- At some point, a developer sifts through that bin of bug reports. When exactly this happens might vary. It’s been a while since I submitted a bug to CCP, so I don’t recall if there’s a severity field or not. Presumably, higher severity bugs would be looked at first.
- Regardless, each bug in the bin is reviewed by someone to determine if it even is a bug, or if it’s expected behavior and the user doesn’t understand that. “Bugs” that aren’t bugs are either discarded or filed as “not-a-bug.”
- For every bug that actually is a bug, a task is added to the TODO pile of whatever work tracking system the devs are using, and that task is given some level of priority from low to critical. (Note: in this context, “TODO” doesn’t mean “will do eventually” but rather, “might do maybe.”
- Development work is divided into “sprints” of usually two weeks or so. At the planning stage of the next sprint, tasks are drawn from the TODO pile, added to the sprint, and assigned to a developer. If the user in Step 1 is lucky, their task gets added to a sprint.
- Each developer works on their assigned tasks during the sprint, and hopefully resolves them. If not, unfinished tasks are returned to the TODO pile or added again to the next sprint.
- At the end of a sprint, the Quality Assurance (QA) team review the changes that were completed. Sometimes there is testing involved, sometimes not. Sometimes that testing can take a while. Software that passes QA is then added to a release candidate. Software that fails QA is returned to the developer for review. This might mean the task goes back into the TODO pile.
- At some point, after X number of sprints, the release candidate becomes the next version of the product and is released to the users.
- If the user in Step 1 is very lucky, their bug has been fixed in the new release.
Depending on a wide range of factors, the time from Step 1 to Step 10 may range from a few days or weeks to a few years or never.
TL;DR: Perhaps adjust your expectations.
I cannot even check the bug report number of my open bugs anymore since CCP removed the tracker.
Only when the bug report is made do you briefly see the number, but once you close that it’s gone.
I’ve had someone ask before what my bug report number was of a certain bug only for me to have to tell them I have no way to retrieve that number.
It’s bad.