Feature #3364
Blocked or Following Issues
| Status: | New | Start date: | 2009-05-15 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: | - | % Done: | 30% |
||
| Category: | Issues | ||||
| Target version: | - | ||||
| Resolution: |
Description
There must be a way to avoid closing or resolving an open issue before its preceders and blockers are resolved or closed.
Related issues
History
#1 Updated by Mischa The Evil about 3 years ago
#2 Updated by Mischa The Evil about 3 years ago
- Subject changed from Bloked or Folowing Issiues to Blocked or Following Issues
- Priority changed from Urgent to Normal
Corrected spelling and priority... ;)
#3 Updated by Jean-Philippe Lang almost 3 years ago
Partially implemented in r2800.
Not sure if an open predecessor should block issue from being closed.
#4 Updated by Mischa The Evil almost 3 years ago
- Category set to Issues
- % Done changed from 0 to 50
Jean-Philippe Lang wrote:
IMHO open predecessors should not block issues from being closed. Imagine a case where we have two issues:Not sure if an open predecessor should block issue from being closed.
- 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...
#5 Updated by Serkan Bayhan almost 3 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.
Example:
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)