Motivation: case when some complicated multicomponent project is split into parts to make managing and following easier (say - because each part have separate versioning/releasing schedule), but nevertheless they are handled by the same people.

Alternative (but maybe overcomplicated): make it possible to configure the project so it dynamically delegates such settings.
--------------------------------------------------------------------------------
Modded the subject to serve as a placeholder issue to collect all the things that are requested to be inherited by sub-projects. Current requests:
* -Users/Members (originally from this issue and #5605 [implemented in version#60])-
* Categories (from this issue, #5358 and #6794)
* Modules (from this issue)
* Settings (from #3900)
* -Project member roles (from #9449 [this seems implemented through #5605, version#60])-
* Documents (from #3470)
* Files (from #3470)

_Edited by Mischa The Evil on 280213-2347; Updated related issues and implemented features_

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

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

--------------------------------------------------------------------------------
I don't believe marking http://www.redmine.org/issues/3470 as the dupe is correct. If anything this would be the dupe. In our install it would be beneficial to inherit at any point, not just during creation. However putting in a mechanism for inheriting would invalidate the need to do so during creation, as it could be done at any point.

I like the idea of having a section in the project setup that lists the parent / child documents and simply ticking that would allow access through that particular project?
--------------------------------------------------------------------------------
Just looking back on my response I might have been a bit hasty.

I am specifically looking at the queries at the moment but would it not be possible to treat queries the same as custom fields, in the sens that they are select-able at the project screen?

You could even include logic such as 'Global' queries (which is already handled) then have a filter down effect where only queries in the parent project are available (automatically enabled or not) in the sub-projects.

This would keep the simplicity of having a check-box style interface (same as custom fields) without having it become too cluttered from queries in every single project being replicated.

The last update before mine was 2 years ago so not sure if this is still being actioned?
--------------------------------------------------------------------------------

relates,Closed,5605,Subprojects should (optionally) inherit Members from their parent
relates,New,6794,Global and inheritable Categories
relates,New,5358,Share Issues Categories for sub-projects
duplicates,Closed,9449,Projects users' roles cascade on sub-projects
duplicates,Closed,3900,Inheritance for Sub projects
duplicates,Closed,3470,Projects should inherit documents and files from sub-projects