Actions
Defect #22342
closedWhen copying issues to a different project, subtasks /w custom fields not copied over
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
My environment:
Environment: Redmine version 3.2.0.stable Ruby version 2.0.0-p481 (2014-05-08) [x86_64-openbsd] Rails version 4.2.5 Environment production Database adapter Mysql2 SCM: Subversion 1.8.9 Filesystem Redmine plugins: no plugin installed
Redmine production.log:
Could not copy subtask #1878 while copying #1874 to #1993 due to validation errors: JobNumber cannot be blank Could not copy subtask #1879 while copying #1874 to #1993 due to validation errors: JobNumber cannot be blank Could not copy subtask #1884 while copying #1874 to #1993 due to validation errors: JobNumber cannot be blank Could not copy subtask #1886 while copying #1874 to #1993 due to validation errors: JobNumber cannot be blank Could not copy subtask #1888 while copying #1874 to #1993 due to validation errors: JobNumber cannot be blank
JobNumber IS there in the subtasks. Both the source and target projects have the same fields.
Copying to the same project works, but copying to a different project has the above error.
Originally discussed here:
Related issues
Updated by Joe Price over 8 years ago
A work around is to copy issues with subtasks using custom fields to the same project and then move the issues to another project.
Updated by Jean-Philippe Lang over 8 years ago
- Subject changed from When copying issues, subtasks /w custom fields not copied over to When copying issues to a different project, subtasks /w custom fields not copied over
- Status changed from New to Resolved
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Fixed in r15318.
Updated by Jean-Philippe Lang over 8 years ago
- Status changed from Resolved to Closed
Updated by Mischa The Evil over 7 years ago
- Related to Defect #11315: When I copy a project it does not copy the issues custom fields' values added
Actions