I would utilize this too.
--------------------------------------------------------------------------------
I would love to see this, as we really need this over at TYPO3...

What are the reasons for the current limitation? And how hard would it be to remove it?
--------------------------------------------------------------------------------
> What are the reasons for the current limitation?

Just to keep it simple.

> And how hard would it be to remove it?

To be efficient this would require to replace projects trees by nested sets.
It's not planned for now.
--------------------------------------------------------------------------------
It would be great (and I think enough in the most cases) if there will be support for at least 3 levels of project nesting.

P.S.: Thank you for your great work! Redmine is super! :)
--------------------------------------------------------------------------------
Hello everybody,

I just wanted you to know that I'm currently working on fixing this, see: http://forge.typo3.org/issues/show/439 for the current status of the patch!
Note that we use a custom startpage plugin, that's why not everything in there is relevant for you.

Greets,
Sebastian
--------------------------------------------------------------------------------
Adding at least a 3rd level (level below Subproject) would be very helpful.
--------------------------------------------------------------------------------
Please see code hacks suggested for this Issue at http://www.redmine.org/boards/1/topics/show/893
--------------------------------------------------------------------------------
I agree that it would be great, but these simple "hacks" won't do the trick.
It's not that simple.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I would like to see that too. It would be a great enhancement. Maybe you could introduce a project type 'category' or something similar too. In my opinion it would be good to have somehow an option to group projects together. Like all website projects in one category, all ruby projects in one categories etc. But, hmm, maybe a tagging system would be better to do that.

Best Regards,
bantu
--------------------------------------------------------------------------------
Hi all,

We have made change to eliminate the 1 level subproject limitation from the *r1797*.

These change start from the http://forge.typo3.org/issues/show/439 patch.

File to change are : app/model/project.rb, app/model/query.rb and app/controller/project_controller.rb.

We replace the child_ids, by the computation of the full child list.
The all the child issues are visible in the gantt and issues report.

Best regards
--------------------------------------------------------------------------------
Hi,
I have applied the patch provided by Jéremié and I am currently Redmine for a complex project. It is working smoothly, apart some minor problems. For example, the Overview page of each project does not show the correct number of issues related to it, because Redmine does not count them recursively.

Any hint to address this problem?

Thanks
Pier Giorgio
--------------------------------------------------------------------------------
+1
It's important for me too.
--------------------------------------------------------------------------------
+1

Agreed, while the patch is nice it would be even better if subprojects can inherit settings up the tree, and list/count items like issues recursively... Just had to go through and update the trackers on 20 projects that were all really descendants of one big project. I know it's a lot easier not to but... the work could be very rewarding in terms of how much time it could save.
--------------------------------------------------------------------------------
+1

It would be most useful to me to be able to handle three levels of projects in redmine.
--------------------------------------------------------------------------------
This will probably happen in 0.9.

Could we open a thread or a wiki page to discuss how to get the most power from this new feature ? I'm thinking of course of version inheritance (#465), but also wiki relations, membership inheritance etc. Generaly speaking, we should define inheritance (parent to children) and accumulation (children to parents) behaviours.
--------------------------------------------------------------------------------
This is committed in trunk at r2304.
Implementation uses "awesome_nested_set":http://agilewebdevelopment.com/plugins/awesome_nested_set plugin which is based on "Nested set":http://en.wikipedia.org/wiki/Nested_set_model model and thus performance should not be affected by hierarchy depth.

Paul, that would be a good thing, you can create a wiki page for this. There are several requests about inheritance, a good start would be to list them all.
--------------------------------------------------------------------------------
I've update my SVN to get this feature but noticed that the "jump to project" combo box has disappeared. Is this by design or is it now configurable?
--------------------------------------------------------------------------------
Please disregard the above. This was a PEBKAC....project jump list appears once users are assigned projects!
--------------------------------------------------------------------------------
I've just updated to the "nested set" branch and everything seems to work.

Can anybody tell me how "save" it is to use this branch for productive environments? Of course I know that there could arise bugs and data corruption, but as we have regular updates I'm more worried about future updates...

Is it possible to do rake db:migrate once this feature has been merged in the stable branches?
--------------------------------------------------------------------------------
You'd better not use the nested_projects branch. It was used to initialy implement the feature, but it won't be updated and will be removed.
If you really want this feature, you can use the trunk.
--------------------------------------------------------------------------------
Is using the trunk-version not a bigger risk than using the nested-only branch? I took a look at the mysql tables changes and because I have worked with nested set before I thought this scheme will stay. So instead of using the trunk with many changes and possible problems I choose the nested set branch.

Sadly, immediately after I tried the nested set branch some co-workes started entering many tickets so know I have no choice but to wait for a public roll-out of this feature in the next stable version and hope I get no data-corruption when migrating.

Could you recommend any behaviour right now? Migrate to trunk? Or wait for a final version and try to migrate? Else I have to explain my co-workers that yesterdays work was for nothing :-)
--------------------------------------------------------------------------------
I pulled the trunk version & it doesn't have the Project nesting..

Anyone idea?
--------------------------------------------------------------------------------
Anyone tried the trunk version (0.8.3)

How to get "Unlimited Project nesting" work with trunk?

Any help will be appreciated.

--------------------------------------------------------------------------------
Nanda Palaniswamy wrote:
> Anyone tried the trunk version (0.8.3)
0.8.3 is latest stable version. Current trunk version is 0.9.x. You can get it from svn: http://redmine.rubyforge.org/svn
Read - [[Download#Latest_source_code|Download - Latest source code]] or [[CheckingoutRedmine#Development-version|CheckingoutRedmine - Development version]]
--------------------------------------------------------------------------------
I just installed RedMine and I really like the unlimited nested project feature. The only problem I encountered so far is that different subprojects can't have the same name. For example, we build a race car every year, and we've got different departments. So our project tree would look something like this:

DUT09
- Electronics
- Suspension
- ...

DUT08
- Electronics
- Suspension
- ...

Right know I have to name them "DUT08" -> "DUT08_Electronics". Would it be possible to allow the same names (or identifiers) here? or to hide the prefix if it's the same as the parent project?
--------------------------------------------------------------------------------
Perhaps I've missed understood either that or I have the wrong branch revision. I'm using r2824 and I still have the problem with a sub project can not be a sub of another sub project.

e.g.

ProjectA
-ProjectSub
--ProjectSubSub

And from what I've read r2824 coming from the main trunk should be the version 0.9 release Jean-Philippe is talking about.

Could someone advise me of what's going wrong here.
--------------------------------------------------------------------------------
Jason van Dyk wrote:
> Perhaps I've missed understood either that or I have the wrong branch revision. I'm using r2824 and I still have the problem with a sub project can not be a sub of another sub project.
>
> e.g.
>
> ProjectA
> -ProjectSub
> --ProjectSubSub
>
> And from what I've read r2824 coming from the main trunk should be the version 0.9 release Jean-Philippe is talking about.
>
> Could someone advise me of what's going wrong here.

I have the same puzzle on it.
I use the version from tags/0.8.5 .but i can not find this feature.
Does it need anything else to make it .
--------------------------------------------------------------------------------
frank huang wrote:
> Jason van Dyk wrote:
> > Perhaps I've missed understood either that or I have the wrong branch revision. I'm using r2824 and I still have the problem with a sub project can not be a sub of another sub project.
> > ...
> > And from what I've read r2824 coming from the main trunk should be the version 0.9 release Jean-Philippe is talking about.
> >
> > Could someone advise me of what's going wrong here.
>
> I have the same puzzle on it.
> I use the version from tags/0.8.5 .but i can not find this feature.
> Does it need anything else to make it .

If you are using Redmine version#11 you don't have the feature since its implemented in the Redmine development version (source:/trunk a.k.a. Redmine version#6) only.
The lack of clarity seems to be caused by the (svn-)revisions.

For example: the Redmine version Frank Huang is using is version#11. If you checkout the source of it directly from the SVN-repo (source:/tags/0.8.5) you actually checkout the tag of version#11 *at revision r2886*. That does not automatically mean that the checkout contains the changeset which is applied with revision r2304 since revision r2304 has been applied only to the source:/trunk.
Redmine version#11 is a [[ReleaseManagement#Point-Release-00x|point-release]] for the current stable 0.8.x-branch (source:/branches/0.8-stable) which does not include changes scheduled for another (following) minor-release (Redmine version#6). The changes for version#6 are applied as said only to the source:/trunk

Hope this explains the thing a bit more...

Kind regards,

Mischa.

--------------------------------------------------------------------------------
Mischa The Evil wrote:
> frank huang wrote:
> > Jason van Dyk wrote:
> > > Perhaps I've missed understood either that or I have the wrong branch revision. I'm using r2824 and I still have the problem with a sub project can not be a sub of another sub project.
> > > ...
> > > And from what I've read r2824 coming from the main trunk should be the version 0.9 release Jean-Philippe is talking about.
> > >
> > > Could someone advise me of what's going wrong here.
> >
> > I have the same puzzle on it.
> > I use the version from tags/0.8.5 .but i can not find this feature.
> > Does it need anything else to make it .
>
> If you are using Redmine version#11 you don't have the feature since its implemented in the Redmine development version (source:/trunk a.k.a. Redmine version#6) only.
> The lack of clarity seems to be caused by the (svn-)revisions.
>
> For example: the Redmine version Frank Huang is using is version#11. If you checkout the source of it directly from the SVN-repo (source:/tags/0.8.5) you actually checkout the tag of version#11 *at revision r2886*. That does not automatically mean that the checkout contains the changeset which is applied with revision r2304 since revision r2304 has been applied only to the source:/trunk.
> Redmine version#11 is a [[ReleaseManagement#Point-Release-00x|point-release]] for the current stable 0.8.x-branch (source:/branches/0.8-stable) which does not include changes scheduled for another (following) minor-release (Redmine version#6). The changes for version#6 are applied as said only to the source:/trunk
>
> Hope this explains the thing a bit more...
>
> Kind regards,
>
> Mischa.

To Mischa~

Thank you very much.I have got it.
But there is another question that how can i make the displaying style of projects to horizontal list like before?
Because we have many projects , and the tree style will make the page scrolled .

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

relates,New,15290,Define subproject nesting depth limit
duplicates,Closed,1989,Multilevel Relationship between Projects
duplicates,Closed,1840,Merge projects and issues classes to allow more hierarchical project structure
duplicates,Closed,1004,Suggestion: Subprojects of subproject...?