[23] in Project_DB
Re: restrict issue categories?
daemon@ATHENA.MIT.EDU (Mike Barker)
Mon Feb 24 16:52:38 1997
To: Bill Cattey <wdc@MIT.EDU>
Cc: tjm@MIT.EDU (Tim McGovern), brlewis@MIT.EDU (Bruce R. Lewis),
project-db@MIT.EDU
In-Reply-To: Your message of "Mon, 24 Feb 1997 16:29:26 EST."
<kn4UUq0GgE6e0AStU0@mit.edu>
Date: Mon, 24 Feb 1997 16:51:31 EST
From: Mike Barker <mbarker@MIT.EDU>
-Tim: Do you think we should have a category for issues?
YES. all we have is name and one line for issues--we need that extra
field. issues really need priority, date opened, date last updated, and
so on, but don't remove the category field.
-Do you think it makes sense to even make a distinction of the
-developer/supplier versus the customer in naming issues?
Frankly, I was thinking of all the other categorizations I've seen
and used with project issues. Source of the issue is usually only
important if you are deciding whether project overrun is paid for
by the customer or absorbed by the developers.
I.e., there are more ways to categorize issues than just the originator
of the issue. Leave the field there and let's learn what ways are useful
for people.
mike
