Planned for 0.7
--------------------------------------------------------------------------------
+1

Sub-projects should inherit versions from their parent and parent
project should combine the roadmaps, activities, etc. of its
children.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Do you have any suggestion concerning the view design ?
I may remove the pagination and display the projects as a simple
indented list (with no table).
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
Yes, it definitely would aid usability.
--------------------------------------------------------------------------------
Thanks.
The main projects list should also be displayed as a tree.
What do you think ?
--------------------------------------------------------------------------------
Thanks for r703, this works really well.
--------------------------------------------------------------------------------
Jean-Phillipe: have you see MantisBT? It groups the project
listings as a heirarchy, e.g.:

* Websites

* oursite.com
* intranet

* Helpdesk

* PCs
* Servers

Being able to display projects like that would IMHo be a huge
usability boost.
--------------------------------------------------------------------------------
Point 3 is done.
I've just committed point 4. For sub-projects, parent project
name is added on project list and project overview.
--------------------------------------------------------------------------------
In fact, for now, there's *one* functionality behind parent/child
project relationship: You can view the subproject issues in the
issue list of the parent project (using the subproject filter
that appears if the project has some subprojects).
I'll try to implement some more.

Thanks.
--------------------------------------------------------------------------------
I'd like to see the repository creation to also use this, I use the parent projects almost as catagories which do not get repositories, the sub projects do, I'd like for the creation of a repository in a child project to create/use a directory by the name of the parent... or the name of the parent + "_Projects" or something so that they dont become branches in the parent's repo.

I'm going to try to hack this solution into my installation, when you get projects via soap.ProjectsWithRepositoryEnabled is there a parent project property returned at all?

--------------------------------------------------------------------------------
I agree this is important for two reasons:

1) having sub-projects inherit their settings will simplify project creation -- especially in large complex project environments.
2) it will allow project management to scale over many sub-projects (expecially with the Gantt rollup feature -- which I think would by default need to include version tracking & many people have indicated the need for this with Versions.

So here is another vote for this to happen. In fact, we are now in the position of needing this to happen. We have the need to manage many sub-projects within the context of a "Parent/Corporate Project" and it's versions and deadlines.

I would be pleased to see if we as a community can define what is needed. (I think for my organization -- just the version/gantt sharing would be enough -- since that is what we need, but other features would be welcome too.
--------------------------------------------------------------------------------
I've got some interest in implementing Item 2 above (inherited project settings).

Because I could see settings management become very complex, I propose:

* Adding a checkbox to all the forms under Settings labeled "Include Subprojects" that is displayed when a project has one or more subprojects. When the box is checked, the settings (or members, or versions...) are modified across all subprojects. This doesn't prevent different settings for subprojects, but does make it easy to "reset" all settings.

* Possibly modify the new project form to automatically inherit settings with a similar checkbox.

Ultimately I could see listing/managing subproject settings under the parent's page; this might be especially useful for project members.

#4128 describes this as well.
--------------------------------------------------------------------------------
+1
--------------------------------------------------------------------------------
+1 . Very important for Redmine that Parent/Child issues have stronger relationships, compared to 2 independent projects. One of the important thing is, that version should be transferable to subprojects.
--------------------------------------------------------------------------------

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

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

relates,New,4128,Copy project settings to subprojects