We're a team that manages infrastructure projects. An example piece of work for us would be - Firewall upgrade, which would have multiple sub-tasks underneath it, such as Procure firewall, rack FW, Configure FW, Implement & Test. We're still trying to work out how best to manage this before we go full roll-out.
At the moment we would manage this in Aha by:
Feature level - FW Upgrade
Requirements Level - All of the sub-tasks
But we are wondering about whether we should use To-do's instead because you can add due dates to them, which helps keep us on schedule. However, you lose a lot of reporting functionality compared to requirements, such as: Time-tracking and notifications to Watchers .
The best approach for us would be to add either due dates to Requirements for time tracking and better reporting on to-do's.
|Release time frame|
This is possible by adding custom fields on requirements. Account administrators can do so by going to Settings -> Account -> Custom fields.
You can also read more about it here: https://blog.aha.io/requirements-custom-fields/