Defect #5053
open
Project deletion thinks 2 projects are related
Added by Bruno Prado over 14 years ago.
Updated about 13 years ago.
Description
This test was done: there were 3 projects (say, teste, teste1, teste2), independent, none was child or father of any other. Project teste had some children and father. All this structure was removed, letting just teste2 and teste3. Now, when I try to remove teste1, Redmine thinks teste2 is subproject of teste1. See images attached.
Files
Clicking Yes, project teste2 is not removed.
Cannot reproduce.. Can you confirm it's gone with 0.9.4 version ? If not, could you provide a dump of your "projects" table ?
Probably, the fields in the projects
table defining the tree structure somehow got corrupted.
You can check if the tree is valid in script/console
by typing
Project.valid?
If this results in something other than true, you can repair the tree using
Project.rebuild!
Any news ? I have a similar error
Any news ? I have a similar error
- Priority changed from High to Normal
Luis Polanco: if you have a similar error, help us track that bug down ;) Give us informations requested at SubmittingBugs, and try what Holger suggested (to run "Project.rebuild!" in a "ruby script/console"). A dump of you "projects" table in the database before and after the rebuild would help a lot too.
Also available in: Atom
PDF