Feature #3364


Blocked or Following Issues

Added by Serkan Bayhan almost 15 years ago. Updated almost 11 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


There must be a way to avoid closing or resolving an open issue before its preceders and blockers are resolved or closed.

Related issues

Related to Redmine - Defect #1740: Actually block issues from closing when relation 'blocked by' isn't closedClosedJean-Philippe Lang2008-08-04

Related to Redmine - Patch #2132: Patch to prevent blocked issues from being closedClosed2008-11-04

Actions #1

Updated by Mischa The Evil almost 15 years ago

Partly duplicates issue #1740 (which is patched in #2132)...

Actions #2

Updated by Mischa The Evil almost 15 years ago

  • Subject changed from Bloked or Folowing Issiues to Blocked or Following Issues
  • Priority changed from Urgent to Normal

Corrected spelling and priority... ;)

Actions #3

Updated by Jean-Philippe Lang over 14 years ago

Partially implemented in r2800.
Not sure if an open predecessor should block issue from being closed.

Actions #4

Updated by Mischa The Evil over 14 years ago

  • Category set to Issues
  • % Done changed from 0 to 50

Jean-Philippe Lang wrote:

Not sure if an open predecessor should block issue from being closed.

IMHO open predecessors should not block issues from being closed. Imagine a case where we have two issues:
  • an issue (issue #2) which relies on a function which is implemented in issue #1 (therefore the issue is preceded by issue #1)
  • the predecessor (issue #1) which implements a new function.

If the following state is true than open predecessors should not block issues:

Issue #2 is fully implemented but only the documentation needs to be completed. In that case the issue -done can be set to 90. The actual function is implemented though thus the predecessing issue (issue #1) (which is preceded by this issue ) should be closeable at this stage.

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...

Actions #5

Updated by Serkan Bayhan over 14 years ago

  • % Done changed from 50 to 30

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.

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.


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)

Actions #6

Updated by Dipan Mehta almost 11 years ago

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.

Is this the end goal? or there is something still more to it?


Also available in: Atom PDF