RELATED IDEAS
Add standard date fields to requirements in Aha! Teamwork
What is the challenge? |
The marketing team is moving into Aha! Teamwork. We are excited to gain more visibility into requirements by tracking them on the workflow board. Much of our work is date driven. Think GtMs, blogs, social posts, SBs. This makes tracking and managing dates vital to stay on track. We currently work around this through extensive use of to-dos or managing smaller tasks at the feature level so we can assign dates and track the timing of work on calendars views etc. |
What is the impact? |
As we move into Teamwork, it is critical for us to see when a requirement is due on cards so we can prioritize work correctly on the backlog management view and track it effectively on the workflow board. Our current solution is to use custom date fields, which is ok as long as all 6 teams use the exact same fields so we can report across teams. The downside is that custom dates don't help with the timeline view. We would LOVE to see requirements on there to create an actionable plan for getting the work done. |
Describe your idea |
Add standard start and end dates to requirements and include requirements on the timeline view. |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
10
MERGED
Add optional date fields or ranges on Requirements
Allow Requirements under features to have Date fields. These could be locked to the feature's date range or allowed to fall outside depending on the organization and how they manage.
This would allow for more granular reporting on Features, or t...
4
Likely to implement
© 2025 Aha! Labs Inc.•All rights reserved
Our use case is different, that Requirements come in through the integration with Jira and represent the status of the work in the dev tools needed to deliver a Feature. Each with Start and End Dates that need to roll up to the Feature.
This roll up is not supported in the Feature and the Start and End Dates on the Feature can only be calculated based on the Release. Having Start and End Dates on Requirements with a calculated option on the Feature to be based on Requirements would give us better accuracy for planning based on data from development.
When I am looking at all my work on the workflow board, much of it is in requirements rather than activities. Often we do not even bring the activity into Teamwork. I need to quickly understand when the work is due so I can plan my work effectively each day/week.