Redmine

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

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?

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

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.

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 ?

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.

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.