Bug 813390

Summary: Cannot delete individual asset – the whole package inadvertently deleted
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Derek Howlett <dhowlett>
Component: BRM (Guvnor)Assignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED UPSTREAM QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GACC: brms-jira, mkranz
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-18 06:23:04 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:
Attachments:
Description Flags
Our Project Src Code. none

Description Derek Howlett 2012-04-17 16:03:16 UTC
Created attachment 578084 [details]
Our Project Src Code.

Description of problem:

Cannot delete individual asset – the whole package inadvertently deleted. So when we tried to delete a process flow (.bpmn) the whole package disappeared.



Version-Release number of selected component (if applicable):
Guvnor (BRMS 5.4.0.Beta2)

How reproducible:
DefaultPackage - Create BPMN 2.0 Asset in Repo, select it, archive it. Then from administration archive the item. Complete package is somehow deleted.

  
Actual results:
DefaultPackage is deleted

Expected results:
Only the BPM asset should be deleted.

Additional info:
o   Cannot delete individual asset – the whole package inadvertently deleted. So when we tried to delete a process flow (.bpmn) the whole package disappeared.

Comment 1 Tihomir Surdilovic 2012-04-17 16:18:21 UTC
I am unable to reproduce this. to delete an asset in guvnor you have to open this asset first. You may be archiving the entire package instead of an individual asset..that's the only explanation I can come up with now.

Comment 2 Lukáš Petrovický 2012-04-18 06:23:04 UTC
Also, this has been reported against Guvnor 5.4 Beta 2 - community releases are tracked in JIRA, http://issues.jboss.org