Subtasks

Registered by Jon Black

All tasks are top-level, meaning that dependencies/groupings aren't very clear. Allowing tasks to be created as sub-tasks binds that task to a parent.

All sorts of things need considering for this:
- handling parent deletion
- handling priority/order in list
- handling due dates (if implemented)
- handling duration

Blueprint information

Status:
Started
Approver:
None
Priority:
Essential
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Drafting
Series goal:
Accepted for 0.1.x
Implementation:
Started
Milestone target:
None
Started by
Jon Black

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.