Project

General

Profile

Actions

Defect #4504

closed

Version Status not upgraded from 0.8.5 -> 0.9.0

Added by Simone Carletti about 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
Projects
Target version:
Start date:
2009-12-29
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

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.


Files

missing-status.png (50.8 KB) missing-status.png Simone Carletti, 2009-12-29 15:17
partial-status.png (67.5 KB) partial-status.png Simone Carletti, 2009-12-29 15:17
Actions #1

Updated by Jean-Philippe Lang about 14 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")
Actions #2

Updated by Simone Carletti about 14 years ago

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

Actions #3

Updated by Andrea Campi about 14 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.

Actions

Also available in: Atom PDF