Workflow, issue-tracking, resolution, whoops

Subject: Workflow, issue-tracking, resolution, whoops
From: "McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com>
To: "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 24 Jun 2014 09:54:12 -0400

I'm sure many of us are unofficial testers, discovering and reporting bugs as we work through the use-and-abuse of our products and document what we find.

Anybody ever report a bug, only to find that your report was a duplicate?

How does the workflow function where you live?
What hoops do you have to jump through, to get your own issue/bug-report quashed as a duplicate of a pre-existing one?

We talked previously about how many steps a workflow should have.
One of our rules (generally sensible) is that the originator cannot resolve an issue.
That's fine, except, neither can a peer, apparently. We have to add it to the workload of a tester or a manager to get it merged or resolved.

The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.

Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.

Learn more:


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


Previous by Author: RE: What is not mandated is forbidden
Next by Author: Re: What is not mandated is forbidden
Previous by Thread: TechWhirl: Technical Communication Recap for June 20, 2014
Next by Thread: Re: Workflow, issue-tracking, resolution, whoops

What this post helpful? Share it with friends and colleagues:

Sponsored Ads