Defect #5053
Project deletion thinks 2 projects are related
| Status: | New | Start date: | 2010-03-11 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Projects | |||
| Target version: | - | |||
| Affected version: | 0.9.1 | Resolution: |
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.
History
#1 Updated by Bruno Prado about 2 years ago
Clicking Yes, project teste2 is not removed.
#2 Updated by Jean-Baptiste Barth almost 2 years ago
Cannot reproduce.. Can you confirm it's gone with 0.9.4 version ? If not, could you provide a dump of your "projects" table ?
#3 Updated by Holger Just almost 2 years ago
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
1Project.valid?
If this results in something other than true, you can repair the tree using
1Project.rebuild!
#4 Updated by Luis Serrano Aranda 12 months ago
Any news ? I have a similar error
#5 Updated by Luis Serrano Aranda 12 months ago
Any news ? I have a similar error
#6 Updated by Jean-Baptiste Barth 9 months ago
- Priority changed from High to Normal
@Luis: 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.