Feature #1847

Copy and Move

Added by Ewan Makepeace about 9 years ago. Updated almost 7 years ago.

Status:ClosedStart date:2008-09-03
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:0.9.0
Resolution:Fixed

Description

We have a family of related subprojects under a parent. Often I will assign the same basic task in each of the subprojects (so that I can see how it goes on the first one, and then schedule the same work on the siblings).

Typically I copy and then move the task from one project to the next, but this feels a bit clumsy... Copy duplicates an issue in the current project and Move moves an existing issue to a different project (but does not copy it). Since Copy is a specialised feature, perhaps it could ask for a project first (default being the current project) and then proceed, doing a Copy and Move if requested?

move_as_copy.diff Magnifier (4.1 KB) Ewan Makepeace, 2009-01-28 05:34


Related issues

Related to Redmine - Patch #2559: Copy on Move option Closed 2009-01-22

Associated revisions

Revision 2313
Added by Jean-Philippe Lang almost 9 years ago

Adds ability to bulk copy issues (#1847).
This can be done by checking the 'Copy' checkbox on the 'Move' form.

Revision 3063
Added by Jean-Philippe Lang about 8 years ago

Adds a 'Move and follow' button on Move/Copy view to be redirected to the created issue(s) rather than the source project issue list (#1847).

History

#1 Updated by Ewan Makepeace almost 9 years ago

We are writing a patch for this plan to add a checkbox to the Move screen "Make a copy" which would move a copy of the issue instead of the issue itself.

#2 Updated by Ewan Makepeace almost 9 years ago

Patch uploaded here: #2559

#3 Updated by Kioma Aldecoa almost 9 years ago

Thanks, this looks like a very useful patch, but I'm not sure how to use it. Is it a diff? Is it a copy of a specific file?

#4 Updated by Jean-Philippe Lang almost 9 years ago

  • Status changed from New to Closed
  • Target version set to 0.9.0
  • Resolution set to Fixed

Feature added in r2313.

#5 Updated by Ewan Makepeace almost 9 years ago

Guys - I messed up with the patches (it was a redmine thing, I tried to save the patch file and saved the HTML page for the file instead...)
Our original patch is attached.

#6 Updated by Emilio Lorenzo about 8 years ago

Hi,

in the diff file, issues_controller.rb section, I replaced:

this:
unsaved_issue_ids << issue.id unless issue.move_to(@target_project, new_tracker,is_copy)

with this:
unsaved_issue_ids << issue.id unless issue.move_to_return_issue(@target_project, new_tracker,is_copy)

otherwise Redmine comes up with a "number of arguments" error when you try to move more than one issue.

#7 Updated by Ewan Makepeace about 8 years ago

  • Status changed from Closed to Reopened

There is one really irritating aspect of 'Move' that I have been meaning to flag for a long time - this report reminded me. After I 'Move' and issue to a new project I invariably want to edit it to:

  1. Assign a Category - Categories are per project so it will normally arrive without a category.
  2. Assign a person - if the users are different between projects I will sometimes need to assign it.

However after the move Redmine drops me into the All Issues list for the source project, meaning I then have to switch projects and search for the newly moved task. This is really undesireable behaviour, I should end up back on the same issue in the new project?

#8 Updated by Jean-Philippe Lang about 8 years ago

  • Status changed from Reopened to Closed

Ewan Makepeace wrote:

However after the move Redmine drops me into the All Issues list for the source project, meaning I then have to switch projects and search for the newly moved task. This is really undesireable behaviour, I should end up back on the same issue in the new project?

New button 'Move and follow' added in r3063.

#9 Updated by ko simo about 8 years ago

Can it be recorded that the issue was copied from former issue in the history?

#10 Updated by Brian Lindahl almost 7 years ago

See Patch #7447 for improvements.

Also available in: Atom PDF