Redmine

I'm not able to reproduce this problem. Here is what I do:

• I've created a required text timelog custom field with no default value
• Time tracking is enabled on the project
• I'm logged in as an admin
• On the project issue list, I right-click on an issue
• I change the issue status from the context menu
• The issue status is changed and the issue list is refreshed

Is there anything I'm missing?

What is strange is that it seems you have a default value of 0.0 for the TimeEntry "hours" attribute.
Maybe that's why the TimeEntry gets saved.

Can you try this in your console:

>> TimeEntry.new.hours
=> nil

Jean-Philippe Lang wrote:

What is strange is that it seems you have a default value of 0.0 for the TimeEntry "hours" attribute.
Maybe that's why the TimeEntry gets saved.

Can you try this in your console:

[...]

I needed some time to get this tested well with a 100% clean trunk checkout (r2696) but here are my results:

In my case the console indeed gives me:

>> TimeEntry.new.hours
=> 0.0

This seems to be most-likely an incompatibility with MySQL 4.1.x since migration 32 (create_time_entries) includes:

    create_table :time_entries do |t|
      t.column :project_id,  :integer,  :null => false
      t.column :user_id,     :integer,  :null => false
      t.column :issue_id,    :integer
      t.column :hours,       :float,    :null => false
      t.column :comments,    :string,   :limit => 255
      t.column :activity_id, :integer,  :null => false
      t.column :spent_on,    :date,     :null => false
      t.column :tyear,       :integer,  :null => false
      t.column :tmonth,      :integer,  :null => false
      t.column :tweek,       :integer,  :null => false
      t.column :created_on,  :datetime, :null => false
      t.column :updated_on,  :datetime, :null => false
    end

but my current schema.rb includes:

  create_table "time_entries", :force => true do |t|
    t.integer  "project_id",  :default => 0,   :null => false
    t.integer  "user_id",     :default => 0,   :null => false
    t.integer  "issue_id" 
    t.float    "hours",       :default => 0.0, :null => false
    t.string   "comments" 
    t.integer  "activity_id", :default => 0,   :null => false
    t.date     "spent_on",                     :null => false
    t.integer  "tyear",       :default => 0,   :null => false
    t.integer  "tmonth",      :default => 0,   :null => false
    t.integer  "tweek",       :default => 0,   :null => false
    t.datetime "created_on",                   :null => false
    t.datetime "updated_on",                   :null => false
  end

This leads me to the conclusion that my DB isn't build correctly and since you're testing on MySQL 5.x and I am testing on 4.x I am to blame it another MySQL-compatibility issue... Though, correct me if I'm wrong...

With regards,

Mischa.

Jean-Philippe Lang wrote:

Fix committed in r3232 for when a default value is set in the database.

Thanks for the fix Jean...