Project

General

Profile

Actions

Bug #2060

closed

Projects based on project types having issues assigned to fixed versions won't get created accordingly

Added by liaham about 1 year ago. Updated about 1 year ago.

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

100%

Estimated time:
Affected Version:
Compatible Redmine Version:

Description

When creating a project which is based on a project type having issues assigned to fixed versions the issues and the versions will be created but issues won't be assigned to the fixed version.


Related issues 1 (1 open0 closed)

Related to Redmine Issue Sync - Bug #2055: Issue synchronization creates more relations than it shouldNew

Actions
Actions #1

Updated by liaham about 1 year ago

The method copy_issues(project) expects a Project and not a ProjectType especially at this lines:

# Reassign fixed_versions by name, since names are unique per project
if issue.fixed_version && issue.fixed_version.project == project
  new_issue.fixed_version = self.versions.detect {|v| v.name == issue.fixed_version.name}
end

Since project.is_a?(ProjectType) # -> true the assignment of issues to the fixed_version won't be executed!

Actions #2

Updated by liaham about 1 year ago

This bug will probably also affect project import!

Actions #3

Updated by liaham about 1 year ago

Try to fix it at ProjectsControllerPatch#prepare_source_project.

Actions #4

Updated by liaham about 1 year ago

  • Related to Bug #2055: Issue synchronization creates more relations than it should added
Actions #5

Updated by liaham about 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 100
Actions #6

Updated by liaham about 1 year ago

  • Status changed from In Progress to Closed
Actions

Also available in: Atom PDF