Project

General

Profile

Actions

Feature #1653

closed

issue category lost when moving projects

Added by Burt Culver over 15 years ago. Updated over 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
Start date:
2008-07-16
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

We are using redmine trunk revision 1645 on a centOS 5.2 server.
mysql 5.0.44
ruby 1.8.7
rails 2.1.0

When we move an issue from one project to another, the category is lost on the issue even though the category exists in both projects.

This is what shows in the logs for the move (X's replace sensitive data):

Processing IssuesController#move (for 127.0.0.12 at 2008-07-16 11:11:13) [POST]
Session ID: XXXXXX
Parameters: {"new_tracker_id"=>"", "commit"=>"Move", "ids"=>["154"], "new_project_id"=>"5", "action"=>"move", "id"=>"154", "controller"=>"issues"}
Redirected to http://XXXXXX/projects/devq/issues
Completed in 0.07481 (13 reqs/sec) | DB: 0.04585 (61%) | 302 Found [http://XXXXXX/issues/move/154]


Files

issue.patch (570 Bytes) issue.patch Hiroyuki Yoshioka, 2008-07-17 17:16
Actions #1

Updated by Hiroyuki Yoshioka over 15 years ago

I guess this is not a bug.

But this patch enables you to do what you want.

Actions #2

Updated by Jean-Philippe Lang over 15 years ago

  • Category set to Issues
  • Status changed from New to Closed
  • Target version set to 0.8
  • Resolution set to Fixed

Fixed in r1697. When moved, the issue will now be reassigned to the category with same name if any.

Actions #3

Updated by Jean-Philippe Lang over 15 years ago

  • Tracker changed from Defect to Feature
Actions

Also available in: Atom PDF