bugs can specifiy other bugs as dependences

Registered by Dan MacNeil

The only thing I miss about blueprints is the abiliy to specify a dependency or co-requisite status on another bug or a blueprint.

It would be uber cool if we could not assign a bug a milestone unless it's pre or co requisite

My head would explode with joy if I could set pre , co and post depenencies via email Something like:

  parent <bug number>
  sibling <bug number>
  child <bug number> <bug number> <bug number>
   done

Use Case:

Lee & Swetha are moving a script to send email reminders from the old code base to the new. A big part of the task is to change paths. It would be cool if their bug was linked to the bug Dan & Mansi are working on to remove hard coded paths from the code.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Curtis Hovey

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.