Project

General

Profile

Actions
Copy link

Defect #5399

closed

Unassigned issues are not visible

Added by Stanislav German-Evtushenko almost 14 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2010-04-29
Due date:
% Done:

90%

Estimated time:
Resolution:
Invalid
Affected version:
0.9.3

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

Download all files
Mysterious_issues.png (123 KB) Mysterious_issues.png Stanislav German-Evtushenko, 2010-04-30 22:06
Mysterious_issues.png (116 KB) Mysterious_issues.png Stanislav German-Evtushenko, 2010-04-30 22:10
rake_test.txt (173 KB) rake_test.txt Stanislav German-Evtushenko, 2010-05-05 08:10
Actions
Copy link
 #1

Updated by Jean-Philippe Lang almost 14 years ago

Please read SubmittingBugs. There's no way I can reproduce this problem.

Actions
Copy link
 #2

Updated by Stanislav German-Evtushenko almost 14 years ago

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

Actions
Copy link
 #3

Updated by Jean-Philippe Lang almost 14 years ago

Thanks but you'll have to investigate on this problem since I'm not able to reproduce with a fresh 0.9.3.

Actions
Copy link
 #4

Updated by Stanislav German-Evtushenko almost 14 years ago

I have backup of previous redmine (0.8-stable) and I can try to repeat migration on wednesday.

Actions
Copy link
 #5

Updated by Muntek Singh almost 14 years ago

I just tested going from a backup copy of 0.8.7 -> 0.9.3 and am unable to reproduce.

Actions
Copy link
 #6

Updated by Stanislav German-Evtushenko almost 14 years ago

I did it again and got the same result. My steps to reproduce:

  1. stop redmine
  2. svn switch http://redmine.rubyforge.org/svn/branches/0.9-stable  # from 0.8-stable
  3. 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
  4. $RUN "$MONGREL_RAILS start -e $RAILS_ENV -d -p $PORT"
Actions
Copy link
 #7

Updated by Stanislav German-Evtushenko almost 14 years ago

Please remove this image. I'll make another one.

Actions
Copy link
 #9

Updated by Stanislav German-Evtushenko almost 14 years ago

Problem isn't in database. I've created new DB and got the same result.
I did rake test and attached the log.

Actions
Copy link
 #10

Updated by Stanislav German-Evtushenko almost 14 years ago

  • % 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.

Actions
Copy link
 #11

Updated by Holger Just almost 14 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid
Actions
Copy link

Also available in: Atom PDF