|
-
Aug 4th, 2008, 03:29 PM
#1
Thread Starter
PowerPoster
[RESOLVED] I need a standardized way to report bugs
Hi everyone - my boss actually asked me to post this question - he knows how helpful you all are to me!
My work environment is such that my customer has too much access to me. And our boss is offsite in another state. I have gotten into trouble numerous times by taking direction from my customer. I figured if he reports a problem to me or wants an enhancement, I'm to do it. But that is not the case. So I am trying to reign him in. It's gotten better, today he emailed me about 5x with "bugs" and suggestions, and copied our boss. He considers that "documentation" or a "change request". But that's not quite how my boss wants the flow to go.
So, can anyone suggest a template for reporting bugs and enhancements? Obviously any bug interfering with daily processing would get immediate attention. But my boss doesn't want me to get pulled off my development work for every little nit. So problems have to be explained -where did they occur, are they recreatable, what is the priority, etc. These would get submitted into a log book of errors that I could pick up every once in a while and devote some time to. What has worked for you?
Thanks!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|