Issue 1320 - Role Observer should be granted without approval
Summary: Role Observer should be granted without approval
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: CEE Rubicon
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-25 18:59 UTC by stx123
Modified: 2008-02-25 14:10 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2001-07-25 18:59:40 UTC
or more general
It should be configurable for a role whether a request to obtain this role has
to be approved by the project owner or not.
Comment 1 Unknown 2001-08-06 16:44:08 UTC
reassigning to my principal account
Comment 2 Unknown 2001-08-09 01:16:59 UTC
Reassigning to support for vetting and routing.
Comment 3 Unknown 2001-08-13 21:17:19 UTC
Hi,

This has been entered internally for tracking as pcn5396, I will keep
you updated on its progress.

Thank you
Kat
Comment 4 Unknown 2001-09-04 18:10:58 UTC
accepting issue
Comment 5 Unknown 2001-11-08 23:13:51 UTC
changing QA contact from bugs@ to issues@
Comment 6 Unknown 2002-01-15 18:46:20 UTC
Reassigning all of kat's open issues to support so that I can go through them.
Comment 7 Unknown 2002-01-15 20:00:24 UTC
Our product management group reports that they are planning a new
feature for our next major release (code-name: Danube): the ability
for the admin to set a "requires approval?" tag for each role.
Comment 8 beland 2002-04-04 05:49:37 UTC
I would add that it is rather arduous to have to join projects before
being able to report bugs on them.  I was half-convinced my browser
was dropping cookies or something (partly because the error "Login
required" is somewhat misleading).  The ability to report bugs
("Observer" status) should be given to all users on all projects by
default.  I've never encountered a Bugzilla variant that required
users to jump through so many hoops.

If it's difficult for people to report bugs, the developers are less
likely to hear about them, and the quality of the project will suffer
as a result.  I've noticed at least one high-profile bug that was
mentioned in a *press review* of OO that was not in the database. 
After having encountered so many obstacles trying to report that bug,
I can see how this could happen.
Comment 9 stx123 2002-04-10 19:31:50 UTC
Hi Christopher,
seems that you detected a bug which is different from my enhancement
request.
A registered user should be able to submit bugs against every
component with being an observer.

But thanks for searching the existing bug database.
Comment 10 stx123 2002-04-10 19:33:08 UTC
To be more precise:
You have to register and login, but you don't have to have a specific
role in a project. That's how it should work.
Comment 11 Unknown 2002-08-21 17:39:40 UTC
closing this issue as the resolution is in the Danube release.
Comment 12 stx123 2002-08-21 17:48:28 UTC
If an item is fixed in a later SC release, please change status to
"resolved/later". Thanks, Stefan.
Comment 13 stx123 2006-04-14 01:35:33 UTC
According to the status whiteboard entry this issue is planned or targeted for
Danube.
In preparation of the upgrade we should see a confirmation that the issues will
be resolved in CEE 3.5.1.
Please set the target milestone accordingly.
Comment 14 Unknown 2006-04-17 21:19:24 UTC
This is still in consideration for future release. Updating SWB.
Comment 15 Unknown 2007-01-05 10:15:17 UTC
To CRM
Comment 16 Unknown 2007-01-08 08:54:44 UTC
Moving this issue to the Resolved Later queue . Since this issue is still in
consideration for a Future Release .
Comment 17 Unknown 2007-09-19 10:31:59 UTC
Updating milestone
Comment 18 Unknown 2007-09-19 10:33:14 UTC
Updating milestone
Comment 19 Unknown 2008-02-25 14:10:39 UTC
Hi

This feature is fixed in Rubicon and I have verified the same on a test box
carrying the latest version. I shall close this case for now. Please feel free
to re-open, if the functionality does not satisfy your expectation when site
gets upgraded to Rubicon version of CEE.

Regards,
Vathsan
Support Operations.