Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311593 - Allow "drag-and-drop" between branches of an artifact hierarchy
Summary: Allow "drag-and-drop" between branches of an artifact hierarchy
Status: NEW
Alias: None
Product: OSEE
Classification: Technology
Component: OSEE Application Framework (show other bugs)
Version: 0.9.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 0.9.5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-04 13:54 EDT by Mark D-B CLA
Modified: 2010-05-05 14:04 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark D-B CLA 2010-05-04 13:54:12 EDT
If I open two Artifact Explorers, on different branches, I can drag an artifact from one to the other and the "Confirm Inter Artifact Explorer Drop" window appears, asking whether I want to introduce the artifact into the destination branch as a new transaction.

Now, this is really clever, as it means that I can copy a piece of work from one branch to another but keep the same artifact IDs, which will make merging and lots of other things easier in the future.

I can select a whole bunch of artifacts, and drag-and-drop them. However, if I do that, I lose their hierarchy. This is the same as if I copy and paste them, so isn't unreasonable.

However, what if I want to copy a bunch of related artifacts from one branch to another, and maintain their hierarchy? If I do a copy and paste special, with the "Include children of copied artifacts" box ticked, I get new artifact IDs, which isn't what I want.

Could we have a new menu option, which is only accessible when a copy is done on one branch and a right-click is then done on another, called "Introduce ...", with the same options as paste-special please? This could then allow whole hierarchies to be copied from one branch to another, maintaining artifact IDs, which would be a good way of achieving re-use when only part of the work on a branch is wanted.

Note: This enhancement may not be necessary depending on the outcome of https://bugs.eclipse.org/bugs/show_bug.cgi?id=311592, which could mean that the hierarchy gets preserved anyway.
Comment 1 Ryan Schmitt CLA 2010-05-05 14:04:16 EDT
What we have to do is eliminate only the relations to artifact IDs that (a) don't currently exist on the destination branch and (b) are not being copied as part of the current operation. 

This might also require a review of the modtype lifecycle for relations; I don't know if we currently use the INTRODUCED modtype for relation links.