Defect #13440
open
Copy multiple issues faild
Added by alain Spriet over 11 years ago.
Updated over 11 years ago.
Description
I have the following error message when I copy two issues at the same time : #377 and #378 : Failed to save 2 issue(s) on 2 selected: #, #.
I found nothing in log file : production.log
I use the same share version in both projects.
If I copy only issue #377 it works fine, If I copy only issue #378 it works fine also.
I have also a “task” tracker and copy multiple issues is works fine
Version description :
Environment:
Redmine version 2.3.0.devel
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.12
Environment production
Database adapter Mysql2
Redmine plugins:
rhodecode_repo 1.1.1
- Category set to Issues
- Status changed from New to Needs feedback
- Priority changed from High to Normal
- Affected version (unused) set to devel
Does this happen when you click 'copy', or when you save the data afterwards?
Errors should now be logged after r11611. Could you update and retry then post the validation errors?
The error happens after these actions :
- select two issues in project "training"
- click right mouse then select copy
- modified the project to "test"
- click on copy, then the error message arrive
we install the release ; 2.3.0.devl on the trunck
Environment:
Redmine version 2.3.0.devel.11621
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.12
Environment production
Database adapter Mysql2
Redmine plugins:
rhodecode_repo 1.1.1
alain Spriet wrote:
[...]
Please post the validation errors like J-PL requested...
I see in production.log : *issue could not be updated or copied: Criticality can't be blank
The criticality is a custom field required but in the initial issue( #377) the criticality is set.
if I modified the criticality before copy I can copied the issue.
If i selected only one issue the copy works fine without modified the criticality before copy. I have the error only if i selected multiple issues without modified custom field required.
Also available in: Atom
PDF