https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292007-09-14T07:13:00ZRedmineRedmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=6652007-09-14T07:13:00ZPhilippe Lachaise
<ul></ul><p>Having a visual representaion of such relationhips would be a<br />big help.<br />With the current implementation listing projects like this would<br />already be a big plus :</p>
<p>project_1<br /> sub-project-1.1<br /> sub-project-1.2<br /> sub-sub-project-1.2.1<br /> sub-project-1.3<br />project_2<br /> sub-project-2.1</p> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=13402008-02-16T16:40:05ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Wont fix</i></li></ul><p>Would add too much complexity when things like roles inheritance will be implemented.</p> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=79702009-03-11T17:42:06ZRichard Pecl
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li></ul><p>Could you reconsider this decision?<br />Such feature is really needed. We have many sub-projects shared between many projects.</p> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=79832009-03-12T12:24:47ZThomas Pihl
<ul></ul><p>If they are shared, are they then really subprojects? Sounds more like they are parallell projects with relations to many other projekts.</p>
<p>/T</p> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=79842009-03-12T12:50:07ZRichard Pecl
<ul></ul><p>They are subprojects. <br />E.g.: we have communication library, this library is used in two different projects. We need to show issues in communication library in both projects, and on each project there must be clear indication, that it depends on the communication library.<br />I know there is a workaround filtering issues on multiple projects, but that solves just part of the problem and is totally out of project-subproject user-friendly concepts.</p>
<p><strong>Could somebody designate what Redmine functionality could be affected/must be changed when implementing this feature?</strong> Where are sub-projects processed and shown, what are the issues, drawbacks?</p>
<p>As roles inheritance has been mentioned - is that implemented already? I don't think it is necessary to have role inheritance if that breaks possible sub-project sharing.</p> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=244802011-01-25T19:43:15ZBrian Lindahl
<ul></ul><p>I've remarked on how we solve the problem of shared components in <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Allow more than one parent project i.e. share subprojects (New)" href="https://www.redmine.org/issues/5283">#5283</a>. In my opinion, this is a better way of handling shared components than allowing subprojects to have multiple parents. It better represents whats truly going on, especially when you bring SCM into the picture.</p> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=256692011-02-26T18:18:50ZEtienne Massip
<ul><li><strong>Category</strong> set to <i>Projects</i></li></ul> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=575622014-07-16T07:27:30ZTomislav ParĨina
<ul></ul><p>This feature has been opened for long time, and was requested many times. It would be great if it would be implemented.</p>
Duplicates that I could find:
<ul>
<li><a href="http://www.redmine.org/issues/9265" class="external">Allow an issue to have multiple parent issues</a></li>
<li><a href="http://www.redmine.org/issues/9197" class="external">Allow more than one parent issue for a single issue</a></li>
<li><a href="http://www.redmine.org/issues/5283" class="external">Allow more than one parent project i.e. share subprojects</a></li>
</ul> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=580882014-08-15T00:10:59ZToshi MARUYAMA
<ul><li><strong>Has duplicate</strong> deleted (<i><a class="issue tracker-2 status-1 priority-4 priority-default" href="/issues/5283">Feature #5283</a>: Allow more than one parent project i.e. share subprojects</i>)</li></ul> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=580892014-08-15T00:12:56ZToshi MARUYAMA
<ul><li><strong>Status</strong> changed from <i>Reopened</i> to <i>Closed</i></li><li><strong>Resolution</strong> changed from <i>Wont fix</i> to <i>Duplicate</i></li></ul><p>Close as duplicate of <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Allow more than one parent project i.e. share subprojects (New)" href="https://www.redmine.org/issues/5283">#5283</a>.<br /><a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Allow more than one parent project i.e. share subprojects (New)" href="https://www.redmine.org/issues/5283">#5283</a> has more discussions.</p> Redmine - Feature #298: Project to subproject relationshiphttps://www.redmine.org/issues/298?journal_id=580902014-08-15T00:13:10ZToshi MARUYAMA
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-2 status-1 priority-4 priority-default" href="/issues/5283">Feature #5283</a>: Allow more than one parent project i.e. share subprojects</i> added</li></ul>