Project

General

Profile

Forums » Help »

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

Added by nick cuneo about 13 years ago

There are multiple properties that can be changed when moving an issue between projects, i.e.
Project:

Tracker:

Status

Priority

Assignee

yet if we change more than one property we get the following error:

Failed to save 1 issue(s) on 1 selected: <projectname>

We've been getting around this by just changing the project name and updating the ticket afterward but I feel this should be working, anyone else run into this problem?

Redmine 1.2.1


Replies (9)

RE: Move issue between projects fails if more than one property changed during move - Added by Mischa The Evil about 13 years ago

I just tested this by hand by moving one issue in project-a to project-b, along with two property-changes (status and tracker), on a test-box running source:/trunk@7970 and wasn't able to reproduce an error like you describe.

RE: Move issue between projects fails if more than one property changed during move - Added by Salim B about 13 years ago

I too can't move issues to another project if I change one of the other parameters.

I'm currently using Redmine 1.1.2, upgraded from 0.9.x where I could move issues as I wanted. I also tried 1.2.2 today.
I can reproduce both with issues created earlier in version 0.9.x or in actual version.

production.log doesn't give me any errors so I get stuck to understand where it fails.

RE: Move issue between projects fails if more than one property changed during move - Added by nick cuneo about 13 years ago

We upgraded from 0.9.x also, so it's possible it is an issue with tickets created in 0.9.x and trying to be moved in a newer version.

RE: Move issue between projects fails if more than one property changed during move - Added by Ivan Cenov about 13 years ago

I successfully moved an issue from one project to another project. Two properties changed: tracker, priority.
Using Redmine test installation on my laptop, current trunk, rev 8143.

Ruby/rails
Ruby 1.8.7
Rails 2.3.14

Plugins:
Author box
Featured Projects
Projects Tree View plugin
Redmine Better Gantt Chart plugin
Redmine Code Review plugin
DMSF
Google Docs Plugin
Redmine Information Plugin
Redmine Light Box plugin
Redmine Local Avatars plugin
Redmine Pastebin plugin
Redmine Project filtering plugin
Redmine Repository plugin
Redmine Theme Changer plugin
Redmine Wiki Gchart LaTeX-style Formula plugin
Redmine Wiki Notes plugin
Issues XLS export

RE: Move issue between projects fails if more than one property changed during move - Added by Salim B about 13 years ago

I made some other tests : moving an issue to a project created after the migration (from 0.9.x to 1.1.2) works fine. I could assign the ticket and change the tracker while moving it.

As I can't see any errors in production.log, is there a way to change log parameters ? (info, verbose, debug or something)?

RE: Move issue between projects fails if more than one property changed during move - Added by Etienne Massip about 13 years ago

Salim B wrote:

As I can't see any errors in production.log, is there a way to change log parameters ? (info, verbose, debug or something)?

You can change them in your config/environment/production.rb.

RE: Move issue between projects fails if more than one property changed during move - Added by Salim B about 13 years ago

Thx for the advice Etienne.
Logs and screenshot added to issue #9797.

Salim.

RE: Move issue between projects fails if more than one property changed during move - Added by Stefan Halter about 13 years ago

Hi all,
as Etienne pointed out in #9797: "Could that be related to (mandatory?) custom fields used in each project?". It worked for me, I had to strip mandatory fields in my aim project.
/Stefan

    (1-9/9)