*** Description of problem After the following action project "test-project" will still be visible to a user with role "analyst" and/or "admin". >>Please enter command (type help to see available commands): add-role-project >>Repository alias:test-repository >>Select project: 1) test-project 1 >>Security roles (comma separated list):developer Result: Role developer added successfully to project test-project >>>>>>>>>>>>>>>>>>>>>>>>>>> >>Please enter command (type help to see available commands): push-changes Result: Pushed successfully >>>>>>>>>>>>>>>>>>>>>>>>>>> *** Additional info Other add-role-XYZ commands hide either OU or a repository.
Recommending we would revisit this for 6.2. Project-level roles are less common than repo-level roles. This might not be trivial to fix (this late in the cycle), and for 6.2 with the asset mgmt feature, by default we'd move to 1 project = 1 repo anyway.
BPMS6.2.0.CR2/EAP 6.4 1) used kie-config-cli.sh to add-group-project on repository1 for project1 to developer 2) created a drl1 on the project1 with package org.kie.example.project1 3) users with role analyst/admin cannot access project1/drl1 and cannot create assets on project1