Bug 1014609

Summary:	Cloning into / creating an existing repository should fail
Product:	[Retired] JBoss BRMS Platform 6	Reporter:	Zuzana Krejčová <zkrejcov>
Component:	Business Central	Assignee:	Alexandre Porcelli <porcelli>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tomas David <tdavid>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.0	CC:	etirelli, lpetrovi
Target Milestone:	ER5
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-06 20:16:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Zuzana Krejčová 2013-10-02 11:43:25 UTC

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).

Comment 1 manstis 2013-10-02 13:53:14 UTC

IIRC you have a couple like this; perhaps they can all be wrapped up together (when you get time!). Thanks

Comment 2 Alexandre Porcelli 2013-10-25 17:44:15 UTC

Just tested, but seems that this issue has been fixed for a while.

Comment 3 Tomas David 2013-12-12 14:44:44 UTC

Verified on BPMS 6.0.0.ER5.