Opened 12 years ago
Closed 12 years ago
#2107 closed defect (fixed)
Incorrect logic used to copy multiple resources across connections
Reported by: | jng | Owned by: | jng |
---|---|---|---|
Priority: | high | Milestone: | Maestro-4.0-maintenance |
Component: | Maestro | Version: | |
Severity: | major | Keywords: | |
Cc: | External ID: |
Description
Consider 2 active connections that are laid out like so:
- Connection A - Foo - Bar - Connection B - FolderA - Layers - Layer1,Layer2,...,LayerN
If we copy Layer1,Layer2,...,LayerN from Connection B into Library://Foo/Bar/ on Connection A, we get the following layout on Connection A:
- Foo - Bar - FolderA - Layers - Layer1,Layer2,...,LayerN
When instead we should be getting this folder structure instead:
- Foo - Bar - Layer1,Layer2,...,LayerN
Basically when multiple resources are copied, their parentage is being retained when they should actually be discarded.
Note:
See TracTickets
for help on using tickets.
Fixed trunk (r7209) and 4.0.x (r7210)