TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Some bug tracking systems separate the escalation levels into groups, so a
user is forced to pick from one of a subset before the issue can be saved
for the next level. In that short list above, for example, I see
Minor/Feature/Trivial being a category that after chosen, may allow
escalation to the next stage: Text/Tweak/Major.
My logic is flawed when trying to see how Crash and Block would be the next
level.
At this point I would appreciate the fact the labels mean something, and
aren't only arbitrary "cool" names that only the developer would understand.
Do ISO standards care what you use for issue categories and severity? I
thought the only requirement for most certification was a documented process
that could be checked against to ensure it is followed, regardless of how
flawed?
Gain access to everything you need to create and publish information
through multiple channels. Your choice of authoring (and import)
formats with virtually any output. Try Doc-To-Help free for 30-days. http://www.doctohelp.com/
LavaCon 2010 in San Diego Sept 29 - Oct 2 is now open for registration.
Use referral code TECHWR-L for $50 off conference tuition!
See program at: http://lavacon.org/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
