Bug 973174 - Instance of panel "Import Workspace" present in "Not assigned panels" section
Summary: Instance of panel "Import Workspace" present in "Not assigned panels" section
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BAM
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: DR6
: 6.0.0
Assignee: David Gutierrez
QA Contact: Jan Hrcek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-11 12:16 UTC by Jan Hrcek
Modified: 2014-08-06 20:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Useless not assigned panel present at the bottom of the page. Consequence: That not assigned panel appears every time the product is installed Fix: Remove the panel from the Showcase workspace and commit the resulting XML file export to Github. Result: Not assigned panel is no longer displayed.
Clone Of:
Environment:
Last Closed: 2014-08-06 20:07:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Unassigned panel instance on the page (30.58 KB, image/png)
2013-06-11 12:16 UTC, Jan Hrcek
no flags Details

Description Jan Hrcek 2013-06-11 12:16:34 UTC
Created attachment 759600 [details]
Unassigned panel instance on the page

Description of problem:
There is an instance of panel "Import Workspace" present in "Not assigned panels" section of the page "Import and Export" in Showcase workspace.

Version-Release number of selected component (if applicable):
Dashbuilder DR5

How reproducible:
always

Steps to Reproduce:
1. Start the application and navigate to workspace "Showcase", page "Import and Export"


Actual results:
On the bottom of the page that there is instance of panel "Import Workspace" in "Not assigned panels" section

Expected results:
The unasigned instance of panel should be delete from the page, in the initial configuration of application.

Comment 2 Jan Hrcek 2013-07-13 08:32:02 UTC
Ok, verified with BPMS 6.0.0.DR6 deployed on EAP 6.1


Note You need to log in before you can comment on or make changes to this bug.