Project

General

Profile

Actions

Defect #1640

closed

Custom boolean field ignoring default value setting

Added by Guy Kaiser about 16 years ago. Updated about 16 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
2008-07-14
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

A custom field of type 'boolean' is displayed as checked/true in the "New Issue" page even though it's default is false/unchecked in the field's properties page. If I look at the custom_fields table in MySQL I can see that the default_value field for the property is 0, so it appears to be saved correctly there.

This is a custom field that was added in the "Custom fields" page, it did not come over from a migration of any sort.

Redmine is running with via a mongrel cluster setup through Apache2.

Software information:
  • db version: mysqld Ver 5.0.51a-3ubuntu5.1 for debian-linux-gnu on i486 ((Ubuntu))
  • ruby version: ruby 1.8.6 (2007-09-24 patchlevel 111) [i486-linux]
  • rails version: Rails 2.1.0
  • redmine version: Redmine 0.7.devel.1645 (MySQL)

I would be more than happy to provide any more information that I can about this issue.

Actions

Also available in: Atom PDF