Is there an accepted way to comment on a bug report and say "Oops, that was my mistake, please ignore that bug report"?

bug oops my mistake ignore the bug I just sent



That will do it

Be better to be more specific: "bug The bug I just submitted about Mindburst is mistaken, please ignore it".

That just adds another bug for the Ephemerals to sift through. They might prefer if you just leave it.

Hm, but then they'll have to actually spend even more time testing out the supposed bug.

I've done that before... I never knew if it was the right thing to do or not though.

from my understanding most of the time they will go "Huh? thats not a bug.. wierd players... and toss it

Wouldn't they go through the bugs in order that they receive them? So, if you mistakenly bugged something, they might try to fix it and realize it was a fluke before ever noticing your second bug...Just speculating though

People have bigged things 6 months back that aren't fixed so I don't know if there is an order to them or if they simply aren't bugs....

Maybe issue yourself? I dunno. That's always my first solution to things like that.

Things can take a while, and they do have a priority list

No, the best thing is to use BUG to note that you were mistaken and specify precisely which bug report you're talking about.

Using ISSUE just forces someone to move it across from issues to bugs, since they go into different places and may be reviewed by different people or at different times, so that's just more work for someone.

Leaving it alone will force someone to actually go test it and try to reproduce it, which wastes a lot of time, and the bug report might just be left to clog up the system -- being unable to reproduce a bug is by no means proof there is no bug, since many bugs are irreproducible in the best of circumstances, and since most bug reports give so little of the pertinent information, it's rarely the best of circumstances.

But adding a new bug saying the old one is a mistake will usually cause them both to get cancelled during the initial "triage" step before it even gets to the coders. Even if it doesn't, when a coder looks at a bug report, they'll usually do a search for other bug reports mentioning the same key words (like a skill name, for instance), so they'll still generally see the "oops" soon enough to save them wasting all that time (and that's why it's important to say what bug report you're retracting, so it'll come up on a keyword search).

We have no bugs that are 6 months old so if something got overlooked, please feel free to re-bug.

Before bugs are even classified by priority and assigned to coders, there is a "triage" process whereby many bugs are dumped that are too vague to understand (blah skill doesn't work, fix it), aren't really bugs (blah is doing X--when X is what its supposed to do), are requests to change skills (I think blah skill should work like this), or some combination thereof. Probably the most common reason a bug is wiped is that it cannot be reproduced. If we can't reproduce a bug, we can't fix it.

Mistakes do get made--bugs can be deleted which shouldn't be or misclassified--but we do work on bugs on a continuing basis along with development, etc. Just remember it is important to be as detailed and clear as possible. Double check that a bug is a bug and that it can be reproduced.

Edit: Er, to get back to the topic at hand, it's perfectly fine to send a bug stating a previous bug should be deleted. As Gwylifar said, make sure it's detailed and clear what bug you are referring to.