Defect #8849

Defaults aren't honored in release 1.2.1 (regression)

Added by pasquale [:dedalus] over 8 years ago. Updated about 8 years ago.

Status:NewStart date:2011-07-19
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Custom fields
Target version:-
Resolution: Affected version:

Description

I have a custom field defined as integer that accepts values between 1 and 100 and has 100 as default.
Today I have installed redmine 1.2.1 and for all issues that was submitted before creation of this custum field, I haven't value =100 (as in previous version of redmine ) but I have the field empty.

This is a regression.

old-behavior.png (226 KB) pasquale [:dedalus], 2011-07-20 09:43

new-behavior.png (59.8 KB) pasquale [:dedalus], 2011-07-20 09:43

History

#1 Updated by Etienne Massip over 8 years ago

Are you sure that the default value was set for already existing issues in previous versions ?

#2 Updated by pasquale [:dedalus] over 8 years ago

Etienne Massip wrote:

Are you sure that the default value was set for already existing issues in previous versions ?

Surely: do you want a screenshot?

#3 Updated by Jean-Philippe Lang over 8 years ago

Can not reproduce. The default value for an integer custom field is present on the new issue form.

#4 Updated by pasquale [:dedalus] over 8 years ago

Jean-Philippe Lang wrote:

Can not reproduce. The default value for an integer custom field is present on the new issue form.

The issue isn't related to new issue form; for example, if I have an issue that was submitted before that I have created the custom field, with previous release querying issues via REST API I see an xml like this (note <value>100</value>):

  <issue>
    <id>46</id>
    ...
    <author name="pasquale" id="3" />
    ...
    <parent id="45" />
    ...
    <custom_fields type="array">
    ...
      <custom_field name="Py-order" id="10">
        <value>100</value>
      </custom_field>
    </custom_fields>

    <created_on>2011-02-11T20:43:52+01:00</created_on>
    <updated_on>2011-02-11T20:43:52+01:00</updated_on>
  </issue>

with last release I have that the custom field is empty (note <value></value> for the same issue)

    <custom_fields type="array">
    ...
      <custom_field name="Py-order" id="10">
        <value></value>
      </custom_field>
    </custom_fields>

Also if I see the isse via browser, now I see the custom field empty, while before I see the custom field with default value;

I hope now is clear.

Ciao.

#5 Updated by Etienne Massip over 8 years ago

dedalus - wrote:

Etienne Massip wrote:

Are you sure that the default value was set for already existing issues in previous versions ?

Surely: do you want a screenshot?

Yes ?

#6 Updated by pasquale [:dedalus] over 8 years ago

Etienne Massip wrote:

Yes ?

Ok?

old-behavior.png
new-behavior.png

#7 Updated by nick cuneo about 8 years ago

We recently upgraded from .96 to 1.2.1 and are experiencing the same problem. Custom fields are no longer using the defined default values when issues are moved to projects without the same custom fields, as they were in the previous rendition.

#8 Updated by Mischa The Evil about 8 years ago

nick cuneo wrote:

We recently upgraded from .96 to 1.2.1 and are experiencing the same problem. Custom fields are no longer using the defined default values when issues are moved to projects without the same custom fields, as they were in the previous rendition.

This doesn't seem to be related to this issue. I think it is rather by design since in the new project the custom field is not available, thus it hasn't a default value.

Also available in: Atom PDF