Created attachment 1133687 [details]
[0] ClaimCycle repo

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
very intermittently

Steps to Reproduce:
Scenario:
1. At the time of BRMS 6.2 installation, created user brmsAdmin as 'admin' role user. started BRMS server and tested brmsAdmin as admin privileges.
2. Created two Repo's - CLaimCycle and Authorisation. brmsAdmin has access to both the repo's.
3. created user analyst1 with 'analyst' role
4. created user analyst2 with 'myCustomRole' role
5. started kie-config-cli.bat and executed below commands.

list-repo
Result:
Currently available repositories:
        Repository ClaimCycle
         scheme: git
         uri: git://ClaimCycle
         environment: {username=brmsAdmin, scheme=git, security:r
         groups: []
        Repository Authorization
         scheme: git
         uri: git://Authorization
         environment: {username=brmsAdmin, scheme=git, security:r
         groups: []
        Repository repository1
         scheme: git
         uri: git://repository1
         environment: {username=brmsAdmin, scheme=git, security:r
         groups: []

>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Please enter command (type help to see available commands):
add-group-repo
>>Repository alias:ClaimCycle
>>Security groups (comma separated list):myCustomRole
Result:
Group myCustomRole added successfully to repository ClaimCycle

>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Please enter command (type help to see available commands):
push-changes
Result:
Pushed successfully
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Please enter command (type help to see available commands):
fetch-changes
Result:
Fetched successfully
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Please enter command (type help to see available commands):
add-group-repo
>>Repository alias:ClaimCycle
>>Security groups (comma separated list):myCustomRole
Result:

>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Please enter command (type help to see available commands):
push-changes
Result:
Pushed successfully
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Please enter command (type help to see available commands):
exit

6. As explained above I have executed 'add-group-repo' and added 'ClaimCycle' and 'myCustomRole'
7. executed 'push-changes' command and tested changes are not reflected.
8. Re-Started server and logged-in with analyst1 user and able to see both the repositories. 
   Logged-in with 'analyst2' user and he is able to see only Authorisation repo. 
   But when I logged-in with the brmsAdmin, able to see only Authorisation repo but ClaimCycle repo rules are copied into  Authorisation repo.

Actual results:
Rules from RepositoryX are visible under RepositoryY when using "Project View"

Expected results:
Rules from RepositoryX are NOT visible under RepositoryY

Additional info:
As you can see in the screenshot, rules from ClaimCycle repo are visible in Authorization repo = this should not happen.

I have reproduced this once, but then I was unable to to repeat it again.