Bug 794357 (JBEPP-1402)
| Summary: | possible to clone or copy system nodes in edit navigation | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Viliam Rockai <vrockai> |
| Component: | Portal | Assignee: | Nick Scavelli <nscavell> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.2.0.CR01 | CC: | dingham, epp-bugs, jmorgan, mcupak, theute |
| Target Milestone: | --- | ||
| Target Release: | 5.2.1.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-1402 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
An issue with node copy or clone behavior allowed users to copy or clone a system node but not delete the node. This was caused by the node already being a system node, and therefore could not be deleted based on context. This issue
has been fixed and included in this release of the product.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-24 02:53:32 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
Viliam Rockai
2011-11-25 17:32:11 UTC
Release Notes Docs Status: Added: Needs More Info Primary SME: Added: theute NEEDINFO: Removed: Nobody Added: Subject Matter Expert Release Notes Text: Added: CAUSE: CONSEQUENCE: FIX: RESULT: NEEDINFO Due Date: Added: 30/Nov/11 Release Notes Docs Status: Removed: Needs More Info Added: Not Yet Documented Release Notes Text: Removed: CAUSE: CONSEQUENCE: FIX: RESULT: Added: CAUSE: Copying system nodes CONSEQUENCE: Copied nodes are also system nodes, and hence cannot be deleted FIX: Not yet fixed RESULT: Link: Added: This issue relates to JBEPP-1399 Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Known Issue Release Notes Text: Removed: CAUSE: Copying system nodes CONSEQUENCE: Copied nodes are also system nodes, and hence cannot be deleted FIX: Not yet fixed RESULT: Added: CAUSE: An issue with node copy or clone behavior allows users to copy or clone a system node but not delete the node. This is caused by the node already being a system node, and therefore it can not be deleted based on it's context. There is no work around for this issue. NEEDINFO Due Date: Removed: 30/Nov/11 NEEDINFO: Removed: Subject Matter Expert Release Notes Text: Removed: CAUSE: An issue with node copy or clone behavior allows users to copy or clone a system node but not delete the node. This is caused by the node already being a system node, and therefore it can not be deleted based on it's context. There is no work around for this issue. Added: An issue with node copy or clone behavior allows users to copy or clone a system node but not delete the node. This is caused by the node already being a system node, and therefore it can not be deleted based on it's context. There is no work around for this issue. Labels: Added: EPP_5_2_1_Candidate Link: Added: This issue relates to GTNPORTAL-2185 Link: Removed: This issue relates to GTNPORTAL-2185 Link: Added: This issue is a dependency of GTNPORTAL-2185 Labels: Removed: EPP_5_2_1_Candidate
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
== ISSUE SEEMS TO BE RESOLVED. ISSUE WAS KNOWN BEFORE. DRAFTED RESOLVE ISSUE RN FOR SME REVIEW ==
An issue with node copy or clone behavior allowed users to copy or clone a system node but not delete the node. This was caused by the node already being a system node, and therefore could not be deleted based on context. This issue has been fixed and included in this release of the product.
Deleted Technical Notes Contents. Old Contents: == ISSUE SEEMS TO BE RESOLVED. ISSUE WAS KNOWN BEFORE. DRAFTED RESOLVE ISSUE RN FOR SME REVIEW == An issue with node copy or clone behavior allowed users to copy or clone a system node but not delete the node. This was caused by the node already being a system node, and therefore could not be deleted based on context. This issue has been fixed and included in this release of the product.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
== ISSUE SEEMS TO BE RESOLVED. ISSUE WAS KNOWN BEFORE. DRAFTED RESOLVE ISSUE RN
FOR SME REVIEW ==
An issue with node copy or clone behavior allowed users to copy or clone a
system node but not delete the node. This was caused by the node already being
a system node, and therefore could not be deleted based on context. This issue
has been fixed and included in this release of the product.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,7 +1,2 @@
-== ISSUE SEEMS TO BE RESOLVED. ISSUE WAS KNOWN BEFORE. DRAFTED RESOLVE ISSUE RN
-FOR SME REVIEW ==
-
-An issue with node copy or clone behavior allowed users to copy or clone a
-system node but not delete the node. This was caused by the node already being
-a system node, and therefore could not be deleted based on context. This issue
+An issue with node copy or clone behavior allowed users to copy or clone a system node but not delete the node. This was caused by the node already being a system node, and therefore could not be deleted based on context. This issue
has been fixed and included in this release of the product.
|