Defect #5399
closed
Unassigned issues are not visible
Added by Stanislav German-Evtushenko over 14 years ago.
Updated over 14 years ago.
Description
After redmine upgraded to 0.9.3 I can't see any unassigned issues. I can see these only on the activity page. If I assing issue to someone it appear on the issues page.
Files
Please read SubmittingBugs. There's no way I can reproduce this problem.
About your application's environment
Ruby version 1.8.7 (i586-linux)
RubyGems version 1.3.6
Rack version 1.0
Rails version 2.3.5
Active Record version 2.3.5
Active Resource version 2.3.5
Action Mailer version 2.3.5
Active Support version 2.3.5
Application root /mnt/data/redmine/redmine-0.8-tmp
Environment production
Database adapter sqlite3
Database schema version 20100221100219
Thanks but you'll have to investigate on this problem since I'm not able to reproduce with a fresh 0.9.3.
I have backup of previous redmine (0.8-stable) and I can try to repeat migration on wednesday.
I just tested going from a backup copy of 0.8.7 -> 0.9.3 and am unable to reproduce.
I did it again and got the same result. My steps to reproduce:
- stop redmine
svn switch http://redmine.rubyforge.org/svn/branches/0.9-stable # from 0.8-stable
RAILS_ENV=production
gem install -v=2.3.5 rails
rake db:migrate RAILS_ENV=$RAILS_ENV
rake db:migrate:upgrade_plugin_migrations RAILS_ENV=$RAILS_ENV
rake db:migrate_plugins RAILS_ENV=$RAILS_ENV
rake tmp:cache:clear
rake tmp:sessions:clear
$RUN "$MONGREL_RAILS start -e $RAILS_ENV -d -p $PORT"
Please remove this image. I'll make another one.
Problem isn't in database. I've created new DB and got the same result.
I did rake test and attached the log.
- % Done changed from 0 to 90
I've found what didn't work. After sqlite3 updated from 3.2.8 to 3.6.2 redmine become works.
- Status changed from New to Closed
- Resolution set to Invalid
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 