Bug 1008503

Summary:	Mandatory group for new repositories - inconsistency
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:	low	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:50 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-09-16 13:41:17 UTC

Description of problem:
Group is only mandatory for new or cloned repositories, if there is some group. If there is no group, it isn't needed.

We should either require the group all the time, or it should never be mandatory.

Comment 1 manstis 2013-09-20 07:50:08 UTC

@Alexandre, IIRC you were changing how the "mandatory" logic worked by adding a flag (instead of checking whether there were any Groups?)

Comment 5 Alexandre Porcelli 2013-10-25 19:14:53 UTC

Issue fixed on Uberfire master and 0.3.x branches:

https://github.com/droolsjbpm/uberfire/commit/f457588f1
https://github.com/droolsjbpm/uberfire/commit/0c7c1fe5b

Comment 6 Tomas David 2013-12-13 15:04:42 UTC

Verified on BPMS 6.0.0.ER5.