Bug 1045129 - Asset created in wrong project after creating a project
Summary: Asset created in wrong project after creating a project
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ER1
: 6.0.1
Assignee: manstis
QA Contact: Zuzana Krejčová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-19 16:44 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: Consequence: While a project is being created, creating a new asset in another project causes the asset to be created in the new project instead. Workaround (if any): User should wait till the new project is completely created before creating another asset elsewhere. New project is complete when user can see the Project screen for the new project. Result: Assets may end up in wrong location.
Clone Of:
Environment:
Last Closed: 2014-08-06 19:57:17 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Zuzana Krejčová 2013-12-19 16:44:25 UTC 
Description of problem:
In ER5, creating a project may take quite some time for some reason (might be something to do with issues found in bug 1036759) - half a minute is no problem.
User is given no indication that anything is happening still. While the project is being created, if he creates an asset in another project, the asset might fall into the new project.


Version-Release number of selected component (if applicable):
BPMS 6.0 ER5


Steps to Reproduce:
1. Create project A, wait for it.
2. Create project B.
3. Without waiting for the project B, create a guided rule in project A.
(Path element in the Create New.. dialog shows path in project A.)


Actual results:
Project B is created and the guided rule is in it's default package.


Expected results:
Project B is created but the guided rule is in the correct package in project A.
Note You need to log in before you can comment on or make changes to this bug.