Problem 16 - PRS does not accept ASSIGNED or RESOLVED.
Summary: PRS does not accept ASSIGNED or RESOLVED.
Status: RESOLVED FIXED
Alias: None
Product: Bugzilla
Classification: Unclassified
Component: general (show other problems)
Version: other
Hardware: Other Other
: P2 normal
Assignee: John.Allison
URL:
Depends on:
Blocks:
 
Reported: 1999-10-04 03:27 CEST by John.Allison
Modified: 2007-04-08 18:35 CEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this problem.
Description John.Allison 1999-10-04 03:27:49 CEST 
Seems to happen when a developer logs on for the first time (to do
this he/she has to get a password, then log in as a developer).  This
has happened twice in my experience.  It accepts "Additional Comments"
but not a change of status.

However, when *I* changed status it was sucessful!!!
Comment 1 John.Allison 1999-10-06 09:47:59 CEST 
This is a "feature".  "Collaborators" do not have as many priviledges
as "developers".  We are looking to see if this is what we really want
or allowing assignees full priviledges.
Comment 2 John.Allison 1999-10-21 07:43:59 CEST 
This turned out to be a distinction between "coordinator" and
"collaborator".  My recommended procedure is to give coordinator
status to those who need it.  This can be done by updating/inserting
into the "entities" table.