Project

General

Profile

Actions

Defect #9797

closed

Move issue between projects fails if more than one property changed during move

Added by Salim B over 12 years ago. Updated over 12 years ago.

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

0%

Estimated time:
Resolution:
Duplicate
Affected version:

Description

*Issue opened regarding forum subject : http://www.redmine.org/boards/2/topics/27807

Issues can't be moved to another project if any other property is changed with (tracker, assignee etc.)
We're only too to reproduce this error from now, and it seems to be related to our environments : we both migrated from 0.9.x redmine version.

- In project created after the redmine migration, I don't meet the issue.
- Actual production is in 1.1.2, but I can reproduce the error when upgrading to 1.2.2.

Feel free to ask me some testing or more logs, as soon as you tell how to get those :)

------------------------
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.4.2
Rack version 1.0
Rails version 2.3.5
Active Record version 2.3.5
Active Resource version 2.3.5
Action Mailer version 2.3.5
Active Support version 2.3.5
Edge Rails revision unknown
Application root /opt/redmine-1.1.2
Environment production
Database adapter mysql
Database schema version 20101114115359
[root@localhost redmine-1.1.2]#


Files

DEBUG-Logs.txt (52.7 KB) DEBUG-Logs.txt Logs (Debug), starting from click on 'Move" Salim B, 2011-12-14 17:31
Capture.PNG (11.8 KB) Capture.PNG Screenshot Salim B, 2011-12-14 17:31

Related issues

Is duplicate of Redmine - Defect #6859: Moving issues to a tracker with different custom fields should let fill these fieldsClosedJean-Philippe Lang2010-11-09

Actions
Actions

Also available in: Atom PDF