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.
If you can indeed change the terminology and definitions to something a bit
more useful, these are the ones I've found in most common usage in the dev
environments I've been in:
Cosmetic: change to interface (text changes, placement of screen elements,
etc.); no impact on functionality; fix when time is available
Minor: Little to no impact on functionality, workarounds available; fix
when time available:
Moderate: impact on functionality or processing, workaround may be
available, small number of users impacted; fix in interim release
Major:severe impact on functionality or processing, no workaround
available, multiple users and/or user groups impacted; fix in patch
Showstopper/Severe/Block (I've seen all three): total failure of system or
functionality, no workaround available, all users impacted; fix in
emergency patch (aka, stop everything else until it's fixed)
if you can't change the terminology, maybe you can apply these severities
to what you're stuck with.
HTH
Connie P. Giordano
The Right Words
Communications & Information Design
(704) 957-8450 (cell)
www.therightwords.com
"It's kind of fun to do the impossible." - Walt Disney
It's been a while since I was a Mantis owner, but I'm pretty sure I
remember
the admin having the ability to decide which levels of severity would be
used and displayed, what alerts would be associated with a given level of
severity and possibly even to change their names.
Mantis is very code-oriented, so the default terms tend to be ones that are
common-use among programmers. Some of them are totally non-applicable when
the system is used to track issues with other types of products (for
example, jet engines).
Gene Kim-Eng
> I can't imagine Mantis not being flexible about the names
> and gradations. It should be just an exercise for the DBM
> to set up whatever terminology your people are accustomed
> to using... or whatever framework they wish to graduate to.
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
[LINK: http://www.doctohelp.com/] 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: [LINK: http://lavacon.org/] http://lavacon.org/
---
You are currently subscribed to TECHWR-L as [LINK: http://mbox.server274.com/compose -dot- php?to=connie -at- therightwordz -dot- com]
connie -at- therightwordz -dot- com -dot-
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-
