Defect #4504

Version Status not upgraded from 0.8.5 -> 0.9.0

Added by Simone Carletti over 12 years ago. Updated over 12 years ago.

Status:ClosedStart date:2009-12-29
Priority:HighDue date:
Assignee:-% Done:


Target version:0.9.0
Resolution:Fixed Affected version:


I just installed and upgraded my Redmine instance from 0.8.5 to 0.9.0 (stable branch).
The application is working well, but I just noticed there's an issue with Project Versions.

It seems the migration didn't update the status field (screenshot 1).
In fact, if I manually open a version and hit update, then the error disappear because the status field is now properly set (screenshot 2).

Also, the version select is not displayed in any existing project probably because Redmine can't find any active version after the upgrade.

missing-status.png (50.8 KB) Simone Carletti, 2009-12-29 15:17

partial-status.png (67.5 KB) Simone Carletti, 2009-12-29 15:17

Associated revisions

Revision 3259
Added by Jean-Philippe Lang over 12 years ago

Set status of existing versions to 'open' (#4504).


#1 Updated by Jean-Philippe Lang over 12 years ago

  • Status changed from New to Closed
  • Target version set to 0.9.0
  • Affected version (unused) set to devel
  • Resolution set to Fixed

I've fixed the migration in r3259.
This problem did not occur with my Mysql 5 database (status was set to 'open' by default). What is yours ?

Please run the following to set blank statuses to 'open':

$ ruby script/console production
Loading production environment (Rails 2.3.5)
>> Version.update_all("status = 'open'", "status IS NULL")

#2 Updated by Simone Carletti over 12 years ago

Running the update fixed the issue.
The database is PostgreSQL.

#3 Updated by Andrea Campi over 12 years ago

This works great, but it's easy to miss if someone had already upgraded to trunk before this commit.
You should really move this to a new migration--and add a "status IS NULL" condition just in case.

Also available in: Atom PDF