Redmine: Issueshttps://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292011-12-28T17:50:34ZRedmine
Redmine Redmine - Defect #9887 (New): Custom fields are not defaulted when issue is moved to a different ...https://www.redmine.org/issues/98872011-12-28T17:50:34ZAlex Kovshovik
<strong>Environment information</strong>
<ul>
<li>MySQL Server 5.1;</li>
<li>Ruby Enterprise Edition 1.8.7;</li>
<li>Rails 2.3.14;</li>
</ul>
<p><strong>Short defect description</strong></p>
<p>When an issue is moved from one project to another, the default value is not set for the custom field defined in the target project.</p>
<p><strong>Longer defect description and example</strong></p>
<p>We have 2 projects: Support and Development. In "Development" project we have a custom field of drop-down type: "Deployment Type" (<em>with 2 options: "Normal" and "Hot Patch"</em>). It is <strong>a required field</strong>, but it is configured with the default value of "Normal".</p>
<p>"Support" project doesn't have this custom field, so when I move an issue from "Support" to "Development" I assume that the value of "Deployment Type" would be defaulted to "Normal", but it instead gives me an error: "Failed to save 1 issue(s) on 1 selected: #NNNN."</p>
<p>After I made "Deployment Type" field optional I was able to move that issue.</p>