Description of problem: If you create or clone a repo under a name that is already used, nothing really happens but you get a success message. Version-Release number of selected component (if applicable): BPMS 6.0 ER3 Steps to Reproduce: 1. Create / clone a repository, fill in name 'NAME'. 2. Make a change - e.g. add a file. 3. Create or clone another repository, but again fill in name 'NAME'. Actual results: 'The repository is created/cloned successfully' alert. The repo contents are the same - new file is still there. Expected results: An alert that the user cannot create or clone an already existing repository or some request for confirmation, that the existing repo should be overwritten (and actually overwriting it then).
IIRC you have a couple like this; perhaps they can all be wrapped up together (when you get time!). Thanks
Just tested, but seems that this issue has been fixed for a while.
Verified on BPMS 6.0.0.ER5.