T6976 proposed some requirements management/tracking/trace-ability features. The resolution of this ticket was that a project/Tag #Requirement could be used to indicate that a specific task is a requirement. This makes sense.
root problem: I need a way to easily distinguish requirements from other types of tasks, and I need a way to show relationships between these requirements.
One feature that may help with this might be a "requirements view", or more broadly a "task hierarchical view."
Projects can all have their own workboards, which helps identify where work is within the process, but a "task hierarchical view" would enable someone to look at a project from a top down approach. This can help pointy-haireds see from a high level what has been accomplished, and what still lies ahead.
The idea is that requirements normally spawn sub-requirements (i.e. sub-tasks), but there is not (or I am unaware) of a view that lets one see the entirety of relationships between tasks within a project, or otherwise.
I imagine the layout looking extremely similar to the normal query layout just with indentation...
- T### Requirement 1 ... date, projects, Assigned
- T### Requirement 1.1 ... date, projects, Assigned
- T### Requirement 1.2 ... date, projects, Assigned
- T### Requirement 2 ... date, projects, Assigned
- T### Requirement 3 ... date, projects, Assigned
- T### Requirement 3.1 ... date, projects, Assigned
- T### Requirement 3.2 ... date, projects, Assigned
- T### Requirement 3.3 ... date, projects, Assigned
Some possible issues:
- What should happen if a task is a sub-task of two separate tasks?
- I'm not sure about the limitations of sub-tasks, but presumably they must be acyclic. If not, this can be much more complicated. (Actually, I tried this and Phabricator just kinda freezes).
- Is there a way to ensure ordering of requirement-like tasks, if that becomes important?