It would be really useful if we had a new reference field on issues specifically for blocking issues.

This could then have some basic automation:

- adding an item to the blockers field on an issue automatically changes its status to postponed
- marking an issue as fixed then checks any issues that have that as a blocker. If these issues had only the fixed issue as a blocker, then their status is returned to active.

Comments

joachim created an issue. See original summary.

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented
Project: Drupal.org customizations » Project issue tracking
Version: 7.x-3.x-dev » 7.x-2.x-dev
Component: Code » User interface

We have parent (and child) and related issues. It would be good to integrate these, so it is easy to change if an issue is blocking or not.

joachim’s picture

joachim CreditAttribution: joachim commented

We do, but we don't use these to mean only blocking issues.

Related issues can be 'about the same sort of thing'.
Child issues would typically block the parent, but a blocker is not always a child issue. For example, on Flag, I've just marked a load of issues as blocked because a patch would touch the same code as another issue that has a patch waiting for review: they are blocked because there's no point working on a patch because it'll get broken when the other patch is committed.

joachim’s picture

joachim CreditAttribution: joachim commented

I was looking for an existing issue, and hey, I filed it 2 years ago...

It would be great to bump this up in priority -- the Drupal core issue queue has taken to using this weird and incomprehensible to newcomers '[PP-N]' to mark when an issue has blockers.

What actually needs to be done for this?