Apache OpenOffice (AOO) Bugzilla – Issue 1320
Role Observer should be granted without approval
Last modified: 2008-02-25 14:10:39 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.
reassigning to my principal account
Reassigning to support for vetting and routing.
Hi, This has been entered internally for tracking as pcn5396, I will keep you updated on its progress. Thank you Kat
accepting issue
changing QA contact from bugs@ to issues@
Reassigning all of kat's open issues to support so that I can go through them.
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.
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.
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.
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.
closing this issue as the resolution is in the Danube release.
If an item is fixed in a later SC release, please change status to "resolved/later". Thanks, Stefan.
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.
This is still in consideration for future release. Updating SWB.
To CRM
Moving this issue to the Resolved Later queue . Since this issue is still in consideration for a Future Release .
Updating milestone
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.