#550 guests able to add when not using forced project

[Jeremy Lockwood]

This might be a feature request rather than a bug based on design intent.

When using multiple projects and a guest account, guests are allowed not allowed to comment on existing bugs, but are allowed to add new bugs. This might be by design, but it doesn't fit my design intent.

I hacked in the following at line 50 of user.cs

// guests shouldn't be able to add bugs at all
if (this.is_guest == true)
{
this.adds_not_allowed = true;
}

If this is by design, the feature request would be to add a Web.config flag we can and with the guest user test.

[Corey Trager]

Logged In: YES
user_id=645778
Originator: NO

It's by design. Could you explain more why you would want somebody to have permission to make a comment on an existing bug but not create a new bug? What's your situation?

[Jeremy Lockwood]

Logged In: YES
user_id=2022918
Originator: YES

Actually this scenario does create a crash error when the guest tries to register a new bug (I forgot that by the time I found the solution). I think it was a null object exception because Guest didn't have "comment" rights on any project. I'm pretty sure I can re-create it if you want to see the error page.

The scenario I ended up with was guest having view only rights, but with an "add new bug" link in the upper left that was broken.

I am implementing the project for a client that wants system for tracking the comment/process history but wants to pre-filter the "Bugs" before they get placed in the system. In effect there is a 4th class of user that can only comment on existing bugs. We can discuss more about their requirements off list if you would like. I have managed to sideways this functionality into BugTracker.net, but so far it isn't a very elegant solution.