I use the Active status as a sort of inbox. Active items need fixed or ignored. If I decide a fix needs some serious code, I file it in our separate development queue. I'm not sure what to do with issues after I've written them up but before the fix has been coded and deployed. If I leave them Active, they clutter up my error inbox and I have a harder time remembering which issues I've already filed. Ignoring isn't quite right. If we determined a fix is in order, the error will almost certainly get logged again before the fix is out. Now Active is cluttered again and I get a noisy email.
Possible solutions include:
- an Inbox view of errors I haven't acknowledged yet. Errors wouldn't reappear in the inbox until I mark the group resolved or ignored.
- an InProgress status that I manually have to move errors out of when a fix is deployed. This behaves much like Permanently Ignored, but my Permanently Ignored status is already cluttered with spider errors and such that make updating status post-deploy painful.
I think I'd prefer an Inbox.