QVCS Enterprise 2.1.21 Admin Tool Glitch?, Maintain Roles does nothing after 2nd update Options

[TGB]

I wonder has anyone else seen or encountered this issue:
When running the QVCSe Admin tool to adjust/modify/delete users from a project (right click on a project user name in right hand pane and click the single entry on the context Menu "Maintain roles..." (see attachment screen shot)
It works fine for the first two users operated on and updated.
The third time when you click on the "Maintain roles..." the UI does not respond, it just leaves the context menu up as if you had not clicked on it. I have to sign out of the Admin tool and sign back in to continue to maintain users.
This is a quite an annoyance when you have a large number of project/users whose rights/roles need to be maintained, especially for me now setting up a new try and buy installation.
Any ideas?

[TGB]

Solved! - Here's the work-around:
Just point at ANOTHER project on the same Server by clicking on it, then click back to the Project you are working on and you get two more shots at doing the "Maintain roles..." function on that Project.
Jim - if you would be so kind maestro sir, please confirm as a bug and advise this group of your findings.
Thank you,
Ted

I wonder has anyone else seen or encountered this issue:
When running the QVCSe Admin tool to adjust/modify/delete users from a project (right click on a project user name in right hand pane and click the single entry on the context Menu "Maintain roles..." (see attachment screen shot)
It works fine for the first two users operated on and updated.
The third time when you click on the "Maintain roles..." the UI does not respond, it just leaves the context menu up as if you had not clicked on it. I have to sign out of the Admin tool and sign back in to continue to maintain users.
This is a quite an annoyance when you have a large number of project/users whose rights/roles need to be maintained, especially for me now setting up a new try and buy installation.
Any ideas?

[Jim Voris]

I can duplicate the defect.... so I should be able to fix it pretty quickly. The workaround you suggest is a good one in the meanwhile.

[Jim Voris]

This is fixed in the 2.1.22 release (now available).