https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292009-05-15T20:42:06ZRedmineRedmine - Feature #3364: Blocked or Following Issueshttps://www.redmine.org/issues/3364?journal_id=92792009-05-15T20:42:06ZMischa The Evil
<ul></ul><p>Partly duplicates issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Actually block issues from closing when relation 'blocked by' isn't closed (Closed)" href="https://www.redmine.org/issues/1740">#1740</a> (which is patched in <a class="issue tracker-3 status-5 priority-4 priority-default closed" title="Patch: Patch to prevent blocked issues from being closed (Closed)" href="https://www.redmine.org/issues/2132">#2132</a>)...</p> Redmine - Feature #3364: Blocked or Following Issueshttps://www.redmine.org/issues/3364?journal_id=93622009-05-18T20:42:14ZMischa The Evil
<ul><li><strong>Subject</strong> changed from <i>Bloked or Folowing Issiues</i> to <i>Blocked or Following Issues</i></li><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>Normal</i></li></ul><p>Corrected spelling and priority... ;)</p> Redmine - Feature #3364: Blocked or Following Issueshttps://www.redmine.org/issues/3364?journal_id=100242009-07-04T12:07:55ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>Partially implemented in <a class="changeset" title="Actually block issues from closing when a blocking issue isn't closed (#1740)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/2800">r2800</a>.<br />Not sure if an open predecessor should block issue from being closed.</p> Redmine - Feature #3364: Blocked or Following Issueshttps://www.redmine.org/issues/3364?journal_id=100532009-07-05T21:41:41ZMischa The Evil
<ul><li><strong>Category</strong> set to <i>Issues</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>Jean-Philippe Lang wrote:</p>
<blockquote>
<p>Not sure if an open predecessor should block issue from being closed.</p>
</blockquote>
IMHO open predecessors should not block issues from being closed. Imagine a case where we have two issues:
<ul>
<li>an issue (issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Listing 5 projects on Welcome page (Closed)" href="https://www.redmine.org/issues/2">#2</a>) which relies on a function which is implemented in issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a> (therefore the issue is preceded by issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a>)</li>
<li>the predecessor (issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a>) which implements a new function.</li>
</ul>
<p>If the following state is true than open predecessors should not block issues:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Listing 5 projects on Welcome page (Closed)" href="https://www.redmine.org/issues/2">#2</a> is fully implemented but only the documentation needs to be completed. In that case the issue <span>-done <em>can be set</em> to 90</span>. The actual function <strong>is</strong> implemented though thus the predecessing issue (issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: permissions if not admin (Closed)" href="https://www.redmine.org/issues/1">#1</a>) (which is preceded by this issue ) should be closeable at this stage.</p>
</blockquote>
<p>I guess this is something that can depend on everyone's individual workflow. My opinion is that Redmine should be kept as flexible as possible. Therefore I'd say to keep actual issue-blocking a feature of the blocking issue-relation only. Though, YMMV...</p> Redmine - Feature #3364: Blocked or Following Issueshttps://www.redmine.org/issues/3364?journal_id=100552009-07-06T07:10:27ZSerkan Bayhan
<ul><li><strong>% Done</strong> changed from <i>50</i> to <i>30</i></li></ul><p>It would be great for us if an issue can be marked to be closed conditionally. For example blokers must be closed or certain %-done level is reached for each related issue or all, there may be some restrictions and of course this feature can be toggled (on/off) from projects settings and/or system wise settings.</p>
<p>And it would be great if some checklist for issues and cattegories. We can check/uncheck standart procedures and each check determines the progress of issue and %-done level.</p>
<p>Example:<br /><pre>
Issue #xxx:
Stereotype: yyyy
[OK] Todo blah blah 1 (%30)
[..] Todo blah blah 2 (%10)
[ ] Todo blah blah 3 (%50)
[OK] Todo blah blah 4 (%50)
[ ] Todo blah blah (%10)
[OK] Todo blah blah (%50)
Done: 85% (30% + (50% of 10%) + %50)
</pre></p> Redmine - Feature #3364: Blocked or Following Issueshttps://www.redmine.org/issues/3364?journal_id=473362013-03-22T15:37:04ZDipan Mehta
<ul></ul><p>As of now - the blocked by issues are not allowed to be closed till the corresponding issues are not closed. This shouldn't be applied, in my opinion, to precede or other relations.</p>
<p>Is this the end goal? or there is something still more to it?</p>