Project

General

Profile

Actions

Defect #1740

closed

Actually block issues from closing when relation 'blocked by' isn't closed

Added by Mischa The Evil almost 16 years ago. Updated almost 15 years ago.

Status:
Closed
Priority:
Normal
Category:
Issues
Target version:
Start date:
2008-08-04
Due date:
% Done:

50%

Estimated time:
Resolution:
Fixed
Affected version:

Description

In r506 issue relations are introduced. In the initial commit four relations are defined:
  1. related to
  2. duplicates
  3. blocks
  4. precedes

As far as I can trace the first (related to) and the fourth (precedes) are implemented in r506 already. The second (duplicates) is implemented in r663 and fixed in r1162, r1183 and r1488.

It seems to me (after trying the demo and my checkout of the latest trunk) that the third relation (blocks) isn't implemented at all after r506. I guess this should behave like described in the commit-message of r506:

blocks: will require to close the blocking issue before closing the blocked issue


Related issues

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

Actions
Related to Redmine - Feature #1755: add "blocked by" as a related issues option Closed2008-08-06

Actions
Related to Redmine - Feature #3364: Blocked or Following IssuesNew2009-05-15

Actions
Related to Redmine - Feature #279: issue dependenciesClosedJean-Philippe Lang

Actions
Has duplicate Redmine - Defect #2888: "blocks" has not implemented.Closed2009-03-03

Actions
Precedes Redmine - Feature #12355: Being able to close blocking and blocked issues in one bulk update operationConfirmed2008-08-052008-08-05

Actions
Actions #1

Updated by Jim Jones almost 16 years ago

+1

Actions #2

Updated by Steven Chanin over 15 years ago

  • Status changed from New to Resolved
  • Assignee set to Jean-Philippe Lang

See #2132 for a patch to address this

Actions #3

Updated by Marcos Vinícius Souza about 15 years ago

Another relation to add:
- belongs to
With this relation, we could make a hierarchy between tickets. In addition, the root ticket could summarize the effort from the child tickets.

Actions #4

Updated by Mischa The Evil about 15 years ago

Marcos Vinícius Souza wrote:

Another relation to add:
- belongs to
With this relation, we could make a hierarchy between tickets. In addition, the root ticket could summarize the effort from the child tickets.

Marcos, your comment does not relate to this issue's subject at all. Your talking about a subject which is discussed on issue #443. If not: then you should open a new issue for your request yourself... :-)

Actions #5

Updated by Mischa The Evil about 15 years ago

  • Status changed from Resolved to 7
  • Priority changed from High to Normal
  • % Done changed from 0 to 50
  • Estimated time deleted (1.00 h)

Corrected fields before tracker-change from feature to defect.

Actions #6

Updated by Mischa The Evil about 15 years ago

  • Tracker changed from Feature to Defect
Actions #7

Updated by Mischa The Evil about 15 years ago

@Jean-Philippe,

I've changed the tracker since this is a feature which is documented as already implemented but it is in-fact not implemented yet.
Patch #2132 implements a fix to adress this issue in a way that if an issue is blocked by another issue, then the available statuses only include statuses that does not have the closed status-attribute set (e.g. New, Assigned, Resolved, Feedback). It also includes updates for the unit tests and fixtures...

Actions #8

Updated by Jean-Philippe Lang almost 15 years ago

  • Status changed from 7 to Closed
  • Target version set to 0.9.0
  • Resolution set to Fixed

Fix committed in r2800.

Actions #9

Updated by Mischa The Evil almost 15 years ago

Jean-Philippe Lang wrote:

Fix committed in r2800.

Great... Thanks!

Actions

Also available in: Atom PDF