A bug in the bug list

We are currently fixing a lot of bugs in our system. They have been there for a while, but it was time to do some cleaning. During intermediate testing I found a bug, which “should have been solved”. So I asked my colleague Frank to help me out here. It turned out we had a bug in our bug list. It has been there for some while, hiding, staying unnoticed, until now.

From: Frank
To: Ronald
Subject: Re: where did we lose sight of this bug? 

Hi Ronald,

I see. It is neither incident#26 nor one the print bugs (incident#36, incident#201, incident#205). It seems that this incident is described in incident#211 and incorrectly was set to duplicate (to incident#200) by Eric last year and therefore is not in the current scope. I will talk to Jack, to clarify whether he can fix it, yet. We will do so, if the solution does not conflict with others.

Best regards, Frank

————————

From: Ronald
To: Frank
Subject: where did we lose sight of this bug?

So we had a bug in the bug list 🙂

Best regards,  Ronald

————————

From: Frank
To: Ronald (VWM)
Subject: where did we lose sight of this bug?

Hi Ronald, 

It seems that we can fix both (the bug in the bug list and the bug itself), without delay in the planning.

Best regards,  Frank

————————

Well, I have a next action on my (long) to-do list: checking all incidents with status “closed (due to duplicate)”.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s