Issue 1303 - Permission to disallow IZ user "guest" to add comments
Summary: Permission to disallow IZ user "guest" to add comments
Status: CLOSED DUPLICATE of issue 1368
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Upgrade (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-23 12:43 UTC by stx123
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

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

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2001-07-23 12:43:18 UTC 
I would like to see a possibility to disallow IZ user "guest" to add comments.
Esp. as this was the behaviour of IZ on t-OOo.
Comment 1 Unknown 2001-07-26 23:57:51 UTC 
Stefan, it is amazing the kind of information you can dig up with a little 

persistence.



It is the default behavior of SourceCast to require a login to allow a 

comment to be added to an issue. That is also true of openoffice.inst. 

However, for some reason, someone deliberately created a user "guest" 

in IssueZilla. (You can see this for yourself if you 'edit users' under Issue 

Tracking.) It's likely that this account was created specifically to allow the 

behavior you now want removed.



The fix appears easy: delete the user "guest." A query run against user 

"guest" reveals, somehow, a lot of issues for which "guest" is the owner. 

Remember, this is all data migrated from the live site. So this situation 

has to exist on the T-OOo site.



So...how would you like to proceed?
Comment 2 Unknown 2001-08-01 17:32:44 UTC 
This is being marked as a dupe of 1368; we have assigned this internally 
as a general "guest permissions" matter.

*** This issue has been marked as a duplicate of 1368 ***
Comment 3 michael.bemmer 2003-03-11 17:18:51 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 4 michael.bemmer 2003-03-11 17:56:50 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details.