0003204: Better handling of project/user rights - JEDI Issue Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0003204	JEDI VCS	Common	public	2005-09-17 05:57	2005-12-29 00:29

Reporter	THuber	Assigned To
Priority	normal	Severity	feature	Reproducibility	always
Status	acknowledged	Resolution	open
Product Version
Target Version		Fixed in Version

Summary	0003204: Better handling of project/user rights
Description	Managing of project/user rights is a bit limited in JVCS 2.4 and should be improved in further JVCS versions. 1. roles should be added for easier administration of larger teams/users with different functions (developers, docwriters, Q&A ...) 2. if there are lot of projects in the repository it's hard to configure project rights. See also 1. 3. it should not be possible to get rw access to a module in a project for which the user has only ro rights by adding it as a shared module to a project for which user has rw rights. 4. Project hierarchy view should only show items in which are projects for which user has access.
Additional Information	please comment
Tags	No tags attached.

Fix in JVCS version	3.0
Releasedocumentation

USchuster 2005-09-17 06:26 manager ~0007940	We should "discuss" the right stuff in the wiki and put the finished concept back in this issue. I've still added "more fine grained rights" to the Roadmap Talk page(http://jedivcs.sourceforge.net/mediawiki/index.php/Talk:Roadmap) in the wiki some time ago.

korecek 2005-12-29 00:29 reporter ~0008250	Hi, after long time (I had not much time) and with big respect to "mediawiki" I did not find a "more fine grained rights" item there :-( . So, as the initiator of the child issue ID:0003193 (see above) I'd like to comment four points here in description: Ad 1.: I have no problems with roles which make easier to administrate a larger teams. I only suppose that it is only additional feature to a current version of JVCS. In the moment I would like to say: There would be very high appreciated if changes in rights and roles will be described (here and/or in documentation) because we have server-based JVCS notificator which should follow changes in new versions. Ad 2.: No comment. (See also 1 ... ) Ad 3.: Shared modules "rw" vs. "ro" access rights: I am not sure here but it sounds as regular feature. But again, please describe new feature in doc. (Note: We have only problem with removing some revisions of a shared module from archive - which is not requested to be in archive further :-( . Not for this issue...I know... ) Ad 4.: Regarding project hierarchy view: there is no problem with such solution (I would like it...) but please show all project hierarchy (no "Unassigned Projects" only) after connection to a project for a user which have "ro" access minimally into the project. Please refresh "Project tree view" after first connection into any project. (I also tested new 2.40 RC3 JVCS Client and its behaviour in Project Tree View is same as in RC2 version unlike RC1 client version - I did not suppose changes there... ;-) ). Vaclav

Date Modified	Username	Field	Change
2005-09-17 05:57	THuber	New Issue
2005-09-17 05:57	THuber	Fix in JVCS version	=> 3.0
2005-09-17 05:57	THuber	Relationship added	parent of 0003193
2005-09-17 05:59	THuber	Status	new => acknowledged
2005-09-17 06:26	USchuster	Note Added: 0007940
2005-12-29 00:29	korecek	Note Added: 0008250