- See how sub-projects are coming through the dump
- See how sub-projects and milestones work now
- enumerate use cases for Phlogiston Milestones (should mostly already be in docs)
- Test needs vs capabilities
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • JAufrecht | T127500 Figure out if sub-projects or milestones can replace Phlogiston's hack of ancestor Milestones | |||
| Resolved | • JAufrecht | T128136 Collect use cases for project/sub-project/milestone |
Event Timeline
Comment Actions
No, it can't. Phlogiston's parent task hack is a way to define which tasks belong to which category by
- using blocked-by to indicate hierarchy (which overloads blocked-by)
- using a designated tag (originally Milestone, now Category) to mark a specific ancestor task as category-defining
and the new sub-projects and milestones are not tools for a hierarchy of tasks within a category, they are tools for a hierarchy of categories.
