https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292011-06-26T15:08:35ZRedmineRedmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=302572011-06-26T15:08:35ZJean-Baptiste Barth
<ul><li><strong>Category</strong> set to <i>Issues</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>7</i></li><li><strong>Assignee</strong> set to <i>Jean-Baptiste Barth</i></li><li><strong>Target version</strong> set to <i>Candidate for next major release</i></li></ul><p>Agreed, definitely. I'll have a look at it since I already worked on issue relations today.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=354032012-01-17T12:39:31ZVictor Engmark
<ul></ul><p>"Related to" is reciprocal to itself. In other words, when such a relation is created, there should be a link from <em>both</em> issues to the other one of the relation.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=355512012-01-25T17:12:30ZChristian Zagrodnick
<ul></ul><p>Victor Engmark wrote:</p>
<blockquote>
<p>"Related to" is reciprocal to itself. In other words, when such a relation is created, there should be a link from <em>both</em> issues to the other one of the relation.</p>
</blockquote>
<p>That is the case but you could still want to build larger circles A -> B -> C -> A.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=361162012-02-16T04:45:41ZFares Abdullah
<ul></ul><p>I had the same problem -</p>
<p>In my case I had an issue, A. I created issue B and set it as related to A. Then I found that B was a duplicate of an existing issue, C, that someone else had created.</p>
<p>I marked B as a duplicate of C, and wanted to relate A to C, and got the "circular dependency" error. I had to manually go and delete the relation between A and B to be able to relate A to C, even though it should not be necessary.</p>
<p>"related to" should allow many different issues related together, as it is not a "dependency".</p>
<p>Cheers and thanks for the great application!</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=389002012-06-10T20:42:31ZJean-Baptiste Barth
<ul><li><strong>Assignee</strong> deleted (<del><i>Jean-Baptiste Barth</i></del>)</li></ul> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=442232013-01-13T20:04:04ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>7</i> to <i>New</i></li></ul><p>Assigned issue with no assignee back to New status.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=489752013-04-30T14:51:35ZLeandro Guida
<ul></ul><p>Here we are having the same problem.</p>
<p>I have an issue A, which is "father" of the issues B and C. When I try to set that C follows B, it gives me the "circular dependency" message.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=490382013-05-02T15:43:15ZRobin McKenzie
<ul></ul><p>+1 "related to" isn't a dependency.</p>
<p>Having the same problem, since we upgraded to the latest version of Redmine.</p>
<p>I've had to advise all our devs to stop using the Related Issues functionality, as this is preventing us setting up tickets with parent/child relationships.</p>
<p>e.g. Create a parent ticket, and two child tickets of this. Attempt to relate the two child tickets - "This relation would create a circular dependency".</p>
<p>Alternatively, create two tickets and relate them to each other. Create another ticket, and then set child A to have this as its parent. Attempt to set child B to have the same parent - "Parent task is invalid".</p>
<p>Would it be possible to get a fix for this prioritised?</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=492512013-05-08T13:35:42ZRalf S.
<ul></ul><p>+1 for this ticket from our side to (using V2.3.1)</p>
<p>It would be very nice, if this fix would get high priority for the next release.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=494602013-05-15T13:12:45ZBenjamin Roberts
<ul></ul><p>+1 for this issue</p>
<p>Environment:<br /> Redmine version 2.3.0.stable<br /> Ruby version 1.9.3 (i386-mingw32)<br /> Rails version 3.2.13<br /> Environment production<br /> Database adapter Mysql2<br />Redmine plugins:<br /> no plugin installed</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=507172013-07-23T12:53:55ZLuke Purdy
<ul></ul><p>+1 for this update.</p>
<p>At the moment I can't create any parent "summary" tasks, for any children who have following dependencies between them (as 4).</p>
<p>It would be helpful if this fix is included as a high priority within the next release.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=527792013-10-24T10:44:59ZRobin McKenzie
<ul></ul><p>Would it be possible to get some feedback as to whether this is being considered for the next release? It was originally set to "Candidate for next major release" over two years ago...</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=555092014-03-24T07:27:06ZAkiko Takano
<ul></ul><p>+1 for this update.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=562492014-05-12T16:12:15ZEgbert van der Wal
<ul><li><strong>File</strong> <a href="/attachments/11590">fix_issue_relations.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/11590/fix_issue_relations.diff">fix_issue_relations.diff</a> added</li></ul><p>How can this still be open when it's such a simple fix?</p>
<p>I applied the attached patch to my Redmine SVN checkout to fix this. Feel free to merge it in. It basically takes the type of relations into account when traversing them and ignores 'copied_to', 'duplicates' and 'relates' relationships as these do not imply any dependency.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=562502014-05-12T16:14:37ZEgbert van der Wal
<ul><li><strong>File</strong> <a href="/attachments/11591">fix_issue_relations.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/11591/fix_issue_relations.diff">fix_issue_relations.diff</a> added</li></ul><p>Sorry, this was the incorrect patch. Attached is the correct version. Please remove the previous patch.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=563942014-05-19T19:13:14ZEgbert van der Wal
<ul></ul><p>Just a tiny update after reading the <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/Patch">Patch</a> page.</p>
<p>The patch I submitted is against revision 13127 of the stable-2.5 branch. I just tested it against trunk, revision 13138 and it also applies cleanly.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=571732014-06-30T04:55:11ZToshi MARUYAMA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/14660">Feature #14660</a>: Excluding "related to" relation from circular dependency check</i> added</li></ul> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=571762014-06-30T04:59:13ZToshi MARUYAMA
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/13914">Defect #13914</a>: Circular dependency issue when issue dependency is set</i>)</li></ul> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=571792014-06-30T04:59:40ZToshi MARUYAMA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/13914">Defect #13914</a>: Circular dependency issue when issue dependency is set</i> added</li></ul> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=576102014-07-18T00:30:29ZJames H
<ul></ul><p>+1</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=583422014-08-28T13:45:04ZUwe Koloska
<ul></ul><p>What about the fix for <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: circular dependency >2 issues (Closed)" href="https://www.redmine.org/issues/7320">#7320</a>? Shouldn't the tests for <a class="changeset" title="Prevent SystemStackError on Issue#all_dependent_issues with circular dependency (#7320)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/4723">r4723</a> and <a class="changeset" title="Prevent SystemStackError on Issue#all_dependent_issues with mutiple circular dependencies (#7320)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/5104">r5104</a> detect the problem described here?</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=583482014-08-29T09:05:22ZUwe Koloska
<ul></ul><p>It looks like <em>related to</em> has a direction!</p>
<ul>
<li>create three tickets 1, 2, 3</li>
<li>create relation 1 -> 2</li>
<li>create relation 2 -> 3</li>
<li>create relation 3 -> 1 gives the circular dependency error</li>
<li>create relation 1 -> 3 succeeds</li>
</ul>
instead of <em>related to</em> you can also use in any combination:
<ul>
<li><em>duplicates</em> (no error with <em>duplicated by</em>)</li>
<li><em>copied to</em> (no error with <em>copied from</em>)</li>
</ul>
<p>Since both are really meant to have a direction their's nothing wrong if there is a circle of all <em>duplicates</em> or <em>copied to</em>, but it should definitely not treat all relations the same.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=584342014-09-05T14:47:08ZUwe Koloska
<ul><li><strong>File</strong> <a href="/attachments/12324">issue_relation_test.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/12324/issue_relation_test.patch">issue_relation_test.patch</a> added</li></ul>attached a test for the current 2.5 branch (but has not changed in trunk) that tests for the following dependencies that should both not be circular:
<ul>
<li>1->2, 2->3, 3->1 (error)</li>
<li>1->2, 2->3, 1->3 (no error)</li>
</ul> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=593672014-10-24T11:12:06ZEtienne Rossignon
<ul></ul><p>+1 to get a fix for this one</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=602042014-12-03T05:50:05ZMischa The Evil
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-4 priority-default" href="/issues/16818">Feature #16818</a>: Allow multiple relationships between two issues</i> added</li></ul> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=607372015-01-08T13:16:59ZMarco Shima
<ul></ul><p>+1 to finally get this fixed. Redmine is only partially useful as long as this major bug exists.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=639142015-05-27T10:54:31ZAnton Statutov
<ul></ul><p>+1. This definitely needs to be fixed.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=668182015-10-23T07:22:19ZNayuta Taga
<ul></ul><p>+1</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=673492015-11-17T09:08:37ZJānis Elmeris
<ul></ul><p>+1</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=685062016-01-12T09:38:27ZGo MAEDA
<ul></ul><p><a class="changeset" title="Can't set parent issue when issue relations among child issues are present (#13654)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/15056">r15056</a> also seems to have fixed this issue.<br />Now I can make A->B, B->C, C->A relations on Redmine 3.2.0.devel.15056.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=685222016-01-13T04:40:16ZGo MAEDA
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>Target version</strong> changed from <i>Candidate for next major release</i> to <i>3.3.0</i></li></ul><p>Fixed by <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Can't set parent issue when issue relations among child issues are present (Closed)" href="https://www.redmine.org/issues/13654">#13654</a>.<br />I am setting target version to 3.3.0 because I think it would be better to list this important issue in Changelog.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=685252016-01-13T05:04:44ZGo MAEDA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/13654">Defect #13654</a>: Can't set parent issue when issue relations among child issues are present</i> added</li></ul> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=686122016-01-16T07:39:15ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li><li><strong>Assignee</strong> set to <i>Jean-Philippe Lang</i></li><li><strong>Resolution</strong> set to <i>Fixed</i></li></ul><p>Thanks.</p> Redmine - Defect #8628: "Related to" reference may yield circular dependency error messagehttps://www.redmine.org/issues/8628?journal_id=709792016-05-17T11:17:16ZRobin McKenzie
<ul></ul><p>Hi, any idea when 3.3.0 will be released?</p>