1st: Great job CCP

beat Chribba by seconds \o/

So what happens to already submitted but unprocessed bugreports?
Will they be forgotten because new system started from scratch?

my first question is: will it be a public bug tracker? (most bugs are not private, people can see if a bug is already filed and can also try to attach additional information to it)

CCP could here once again go a step further and do what for example open source communities are doing with great success. Yes there are bugs which should not be public once they are filed but they have to be reviewed anyway.

No our bug tracker will not be public. It would help with dupes but that's pretty much all it would help with, as well as causing a fair few headaches that aren't really worth going into.

No our bug tracker will not be public. It would help with dupes but that's pretty much all it would help with, as well as causing a fair few headaches that aren't really worth going into.

So in dev blog first BR files in november 2003, first one that was a proper bug, number 62, filed the month before ...

But will I be able to see and add comments to bugs I reported myself? That has always been my biggest annoyance with the old system; you couldn't simply add an extra comment for more details. And the comment from support would end up in the issue either.

Can we expect work on the Petitions system soon? Every time I file a petition, it freezes my client up for about a minute.

I thought about filing a bug report about not being able to report bugs for two weeks but then realized it would be like some of my other bug reports and never read/acted upon/followed up anyway.

Instead it sounds like we should just post gamebreaking bugs in public instead.

Here's some of my recent favorites which CCP never bothered to reproduce, fix or reply to (pick one):

bug 162983, character missing in docked list. logging in multiple clients sometimes you cannot see a character (of yours) that you KNOW is docked in the same station as you (because you have both clients open), despite that character showing in local. ccp closed it because they couldn't reproduce and LALALALALA THERE IS NO RACE CONDITION IN THE UI I CANT HEAR YOUUUU

bug 162982, a bug IN THE BUG REPORTER. when you have multiple accounts/clients, and you use the IGBR, and attempt to submit a bug report, the default account name may be a different account than the character/account you're logged into! while not harmful, totally absurd to have bugs in the bug reporter. gg CCP. status: ignored

bug 161967, standings not displaying properly in local. when you login the local list often has way too many people displaying as neutral instead of proper standings, and you have to minimize/remaximize local to correct it. didn't want those standings anyway. old, obvious, and annoying bug? ccp knows what to do -- status: ignored.

Have fun with jira. I suggest you do not import any of the old bugs, and chalk up the ignoring and non-fixing to the infrastructure transition instead of having insufficient staff handling reports of players who bother to go through proper dev channels to help you fix this damn game.

So, I had a look at your bug reports. The non repro one - 4 separate testers tried to repro with the information you gave, and couldn't. That's a nonrepro over 23 separate attempts using varying conditions. Note the "sometimes" in your statement about the defect - some issues with varying repro rates can be very difficult to reproduce and we only have so much time to allocate to each issue.

The issue you find with the bug reporter isn't actually an issue at all, it's by design, and ultimately changing anyway.

Unfortunately the 3rd issue just looks like it hasn't been gotten around to yet. It's not that it's being ignored, but we are only so many It is very well written though - kudos to you!

It's interesting how a dev blog about bugs, is the first link ever on the EvE client launcher whose title is bugged... and unclickable.

See, from the replies via the existing system all I got was a "can't repro, closed". Not "had 4 separate dudes" or "insufficient time" or "maybe in the future, leaving open". It was as if CCP was pretending there was no bug, instead of marking something difficult to reproduce as a low priority. More of a communication issue than a QA issue (thanks for the reply). I know race conditions can be a pain -- had to deal with those in Garpa Topographical Survey in the past.



Yeah. It was a bug filed out of frustration as I was in the process of reporting a different bug. Now irrelevant since you're changing the IGBR.



This is probably the one that would have the largest impact on the most players anyway. Please send it to a team for a fix. Thanks!

Not my department, but if the client freezes I assume you're uploading files? It's not great behaviour I admit...

I've seen Jira used in another MMO for bug reporting and it was FAR from average player/end-user friendly. It had lots of features for the programmers/devs to track issues but it was a maze to navigate and understand. I suppose this could have had something to do with how it was set up for that environment but, will your new system be friendly for us non-programmer types?

Hope things go well changing over to JIRA.

Not my department, but if the client freezes I assume you're uploading files? It's not great behaviour I admit...

For those, who did not receive any replies to bug reports at all: Please make sure, that the e-mail address is active, which is connected with your account.

So, I had a look at your bug reports. The non repro one - 4 separate testers tried to repro with the information you gave, and couldn't. That's a nonrepro over 23 separate attempts using varying conditions. Note the "sometimes" in your statement about the defect - some issues with varying repro rates can be very difficult to reproduce and we only have so much time to allocate to each issue.

The issue you find with the bug reporter isn't actually an issue at all, it's by design, and ultimately changing anyway.

Unfortunately the 3rd issue just looks like it hasn't been gotten around to yet. It's not that it's being ignored, but we are only so many It is very well written though - kudos to you!

I made a couple of bug reports on my Dscan needing to be opened up every single time i undock..

Both times the replies i got were "No it doesn't"


I wasn't impressed.

The first bug reports were filed on 15th November 2003 as a test to the system. The first player filed bug report that we found was bug report 62, filed on the 26th October 2003

it was reported after last year summer update!!!!!!!!!

So.... with migrating the bug reports to the community site.... those of us experiencing the 324 Error with logging onto all of the EVE websites will no longer be able to access bug reports. Forums only still works for some of us because of cookies that still magically work. So after that, we're left with emailed petitions I guess.

I've got bug report 158874 and bug report 163663 along with a bunch of forum activity on this issue. Slowly but surely I'm losing my ability to communicate this issue to you guys.....

I did not get an update when 143109 was flagged as not reproducable on the bugs front page. This is probably because it was attached to a defect. As a matter of fact, when looking at the report it self, it still says attached to defect.

Return-path: blah
...
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_01BD_01CE0F48.8A792460"

Hello $username, here-is-a-BR-tag Thank you for your bugreport titled ...

We have a high priority internal defect for this issue.



Yeah, this is how the old system worked - it did not propagate the exact state of the internal defect to the bug report. Unfortunately I cannot promise, that you will get more information with the new system, but I hope that there will be less confusion. More details about this should be in future DevBlog on this topic.

Could you give me an update on it though? (143109) Really, REALLY want to know what has been tried (Did a BH/dev actually try more than just installing a job?) I don't care about the materials I lost, I just want to know that it has been locked at properly.

Materials disappearing shouldn't just be ignored, just because you tried to install a manufactering job 100 times when you need to have the process delayed by the server.

I don't know exactly how the dev tried to reproduce it. From a quick glance at the defect I can understand that it would be quite difficult to find the correct type of lag to reproduce it (assuming that it was caused by lag).

Yes, the mailbox is being read for sure. Please send all security relevant information there.

We are not pushing out too many updates to EVE over the next few weeks, and donGÇÿt anticipate many new issues arising.

We are not pushing out too many updates to EVE over the next few weeks, and donGÇÿt anticipate many new issues arising

Firstly, the existing bug reporting site will be no longer be used to collect EVE bug reports. It didnGÇÿt fit with our modern web presence, so our wonderful web team Roundhouse Kick are redesigning new pages from scratch to be a better tool for players that want to let us know about issues they encounter. As a consequence of this, we will also be disabling the In Game Bug Reporter (IGBR) located in the Help menu, until Team Superfriends has it ready to work with our new system. This all means that we will effectively be GÇPgoing darkGÇ£ on bug reports for a couple of weeks, meaning that any reports that you create before we go live with the new solutions, will not be processed.

What dunce decided this was a reasonable course of action?

Normal practice would to wait until the new system was ready before disabling the old one.

As I mentioned in the devblog, we don't anticipate introducing any serious issues, and even then we still have the issues forum.

If you can anticipate introducing serious issue, you wouldn't need any bug reporting system. There were a few bugs introduced with the July 2nd patch; one of which affects a great number of industrialist in the game. That would be the ability to remotely split stacks when making a contract. From the sounds of it, there is little likelihood of those bugs getting fixed any time soon.

If you can anticipate introducing serious issue, you wouldn't need any bug reporting system. There were a few bugs introduced with the July 2nd patch; one of which affects a great number of industrialist in the game. That would be the ability to remotely split stacks when making a contract. From the sounds of it, there is little likelihood of those bugs getting fixed any time soon.

Unfortunately the new defect tracking system is not compatible with the old bug reporting site. The defect tracking system had to get rolled out when it did so as to not impact a release cycle, but the pages and igbr weren't ready, so going dark was the option. As I mentioned in the devblog, we don't anticipate introducing any serious issues, and even then we still have the issues forum. FYI, saying "person" or "developer" in place of your redundant insult would have made your post 100% more pleasant to reply to.

The above underlined & bolded statement is a colossally stupid thing to say. Or did you really mean to imply that there are occasions where CCP anticipates introducing serious issues but proceeds anyway?

Unfortunately the new defect tracking system is not compatible with the old bug reporting site. The defect tracking system had to get rolled out when it did so as to not impact a release cycle, but the pages and igbr weren't ready, so going dark was the option. As I mentioned in the devblog, we don't anticipate introducing any serious issues, and even then we still have the issues forum. FYI, saying "person" or "developer" in place of your redundant insult would have made your post 100% more pleasant to reply to.

how vigilant EVE players can continue to help us to identify and squash pesky bugs and defects.

This all means that we will effectively be GÇPgoing darkGÇ£ on bug reports for a couple of weeks, meaning that any reports that you create before we go live with the new solutions, will not be processed.

I would think it pertinent that seeing as you are unable to process bug reports at the moment, that you disable the in-game bug reporting system.

I am sure you would not want to waste the time of players who take the time and effort of reporting such issues.