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.

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.

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!

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.

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.

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.

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.

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.