|Anonymous | Login | Signup for a new account||2019-04-25 20:52 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007362||TestLink||Users and Rights||public||2015-12-02 14:36||2015-12-03 11:39|
|Priority||high||Severity||major||Reproducibility||have not tried|
|Product Version||1.9.13 (2015 #1)|
|Fixed in Version||1.9.14 (2015 Q3)|
|Summary||0007362: Changing Project/Plan Roles using Search field|
|Description||The screen Assign Test Project Roles (as well as Assign Test Plan Roles) in User Management now contains the field Search (added in version 1.9.13).|
When this field is used the Update operation removes all rights for all the users of given project leaving only the rights for filtered users.
The detailed scenario for Test Projects is explained below. The same problem holds for Test Plans.
|Steps To Reproduce||1. Go to User Management/Assign Project Roles|
2. The first user has the role 'leader', the second user has the inherited role 'guest', see image attached
3. Type in Search field 'abe' to filter the second user
4. Change his role to 'leader'
5. Press 'Update' button
6. Now the second user is 'leader'
7. The first user is modified to inherited role 'no rights'
It is not the expected result - the role of the first user should not be modified when the role of second user is changed
|Additional Information||If we don't use the Search field the operation is performed correctly.|
I.e. if we omit the step 3 (when there are a lot of users paginate instead of searching) at the step 7 both users are 'leader'.
Thus, there is a workaround (avoid using Search), but it is very inconvenient when the number of users is big.
|Tags||No tags attached.|
|Database (MySQL,Postgres,etc)||MS SQL|
|QA Team - Task Workflow Status||TBD|
|Attached Files|| assignroles001.PNG [^] (29,910 bytes) 2015-12-02 14:36
edited on: 2015-12-02 16:18
1) search before posting is a MUST
2) please get 1.9.14, install and retest
I confirm that the bug is fixed in 1.9.14.
Comments (@param...) are not up to date :-)
>>Comments (@param...) are not up to date :-)
what does this means? is near impossible to understand this kind of comments
|2015-12-02 14:36||abIng||New Issue|
|2015-12-02 14:36||abIng||File Added: assignroles001.PNG|
|2015-12-02 16:18||fman||Note Added: 0024328|
|2015-12-02 16:18||fman||Note Edited: 0024328||View Revisions|
|2015-12-02 16:19||fman||Assigned To||=> fman|
|2015-12-02 16:19||fman||Status||new => feedback|
|2015-12-03 10:43||abIng||Note Added: 0024332|
|2015-12-03 10:43||abIng||Status||feedback => assigned|
|2015-12-03 11:39||fman||Note Added: 0024333|
|2015-12-03 11:39||fman||QA Team - Task Workflow Status||=> TBD|
|2015-12-03 11:39||fman||Status||assigned => closed|
|2015-12-03 11:39||fman||Resolution||open => fixed|
|2015-12-03 11:39||fman||Fixed in Version||=> 1.9.14 (2015 Q3)|
|Copyright © 2000 - 2019 MantisBT Team|