MantisBT - TestLink
View Issue Details
0005157TestLinkNew Featurepublic2012-08-21 04:482012-08-21 08:04
kjaware 
 
normalminoralways
newopen 
1.9.3 (2011 Q3 - bug fixing) 
 
MySQL
TBD
0005157: Provide project selection on user creation screen
Whenever we create new user, this user by default got access to all the projects. If the user should not have access to other projects then such kind of access needs to be set up separately.

Enhancement:
Can we provide project list on create user screen itself? Two sections will be there Available projects and Assigned Projects and user will select them as per the requirement. (In similar manner we add platform to test plan.)


Security perspective this is very useful enhancement.
Precondition: Multiple projects created into testlink

Steps:
1. Login to Testlink
2. Go to User Management
3. Click on create user button
4. Enter all required details
5. Click on Save
6. Login with new user
7. Observe the project access

Actual Result: New user has access to all the projects by default.

If the new user should have access only specific projects then project level access needs to be set accordingly by selecting the projects one by one.
This is very tedious task when more number projects are there and number of users needs to be created with specific access.

No tags attached.
png UserCreation.png (39,870) 2012-08-21 05:17
http://mantis.testlink.org/file_download.php?file_id=2800&type=bug
png
Issue History
2012-08-21 04:48kjawareNew Issue
2012-08-21 05:17kjawareNote Added: 0017134
2012-08-21 05:17kjawareFile Added: UserCreation.png
2012-08-21 08:04fmanNote Added: 0017135
2012-08-21 08:05fmanNote Edited: 0017135bug_revision_view_page.php?bugnote_id=17135#r2008

Notes
(0017134)
kjaware   
2012-08-21 05:17   
Please refer attached screenshot for suggested enhancement on user creation screen
(0017135)
fman   
2012-08-21 08:04   
(edited on: 2012-08-21 08:05)
>> Actual Result: New user has access to all the projects by default.
only to all PUBLIC test projects

>> Whenever we create new user, this user by default got access to all the
>> projects. If the user should not have access to other projects then such kind
>> of access needs to be set up separately.
If enough that you create all test projects like PRIVATE instead of PUBLIC, this way new created users HAS NO POSSIBILITY to access test project => this solves part of your request.

User - Test project assignment exists ONLY WHEN you work with PRIVATE TEST PROJECTS, is you work with PUBLIC test projects only way to BLOCK a user access is to assign <NO RIGHTS> role for this user for this specific test project.