Project

General

Profile

Copying an issue leaves it in the closed state rather than switching to the default state

Added by Martin Studer about 11 years ago

We're currently facing an issue where a closed issue that is copied ends up already in the closed state, although the corresponding user does not have the rights to move an issue into that state. I would except a copied issue to always end up in the default state (in this case New). Is there a way to control this behavior? Our Redmine installation details are:

Environment:

Redmine version 2.3.0.stable
Ruby version 1.9.3 (i386-mingw32)
Rails version 3.2.13
Environment production
Database adapter SQLServer

Redmine plugins:

redmine_default_assign 0.2.0