Bug 142447 - [team] RSE Team View should support copying, moving connections and filters
Summary: [team] RSE Team View should support copying, moving connections and filters
Status: ASSIGNED
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: David Dykstal CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-18 05:00 EDT by Martin Oberhuber CLA
Modified: 2007-05-24 09:08 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2006-05-18 05:00:09 EDT
Currently, connections can only be associated with team profiles from the Remote Systems View (Contextmenu > Move or Copy).

It seems more intuitive to do this in the RSE Team View (e.g. Copy&Paste connections, drag & drop them to a different team profile etc).
Comment 1 David Dykstal CLA 2006-05-19 07:51:53 EDT
I propose that we not name this the "Team View" but name it the "Profile View" as well. Comments?
Comment 2 David Dykstal CLA 2006-09-19 22:10:30 EDT
Function will be added after release 1.0
Comment 3 Martin Oberhuber CLA 2006-11-10 18:06:08 EST
Need to investigate - Implementation not planned yet.
Comment 4 David Dykstal CLA 2006-11-17 16:42:54 EST
We should probably split this into a couple of work items:
(1) Move/Copy/Delete connections and filter pools between profiles - done in the "team" view.
(2) Move/Copy/Delete of filters in filter pools from both the "team" view and the "remote systems" view -- See bug 160402. I'm not sure it makes sense in the "remote systems details" view.  

Moving both connections and filter pools between profiles poses problems in that connections contain references to filter pools. A connection can reference a pool in another profile and if that profile disappears (or is made inactive, or isn't loaded) those references are unresolved (or broken). Broken references should not show up in the tree but they should continue to exist.

If a connection is moved then it should continue to reference the same filter pools. However, if a pool is moved, should references to it from other connections be updated or should they break? If we choose to fix automatically fix the references then should we fix those for connections in inactive pools as well? We'll not be able to fix those for connections in unloaded profiles.

This means we should probably display broken filter pool references in the "team" view and allow the user to repair them.