RELATED IDEAS
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 to have Features automatically set a date range based on each Feature's requirements opening a new workflow process to build features from requirements or vice versa. Lastly this would provide deeper use of reporting from Aha! without having to deal with the external work of combining spreadsheets from project teams.
Use case: As a business analyst or product owner, I want a method to visualize the date ranges of requirements as they relate to features within a roadmap or report so I can better visualize when requirements will be completed for a given feature.
Hi Austin,
Thank you for the reply, I wasn't aware I could add the custom field to requirements. Is there a link available that would show me how to accomplish this?
Hi Travis, thank you for the idea. I would love to understand more about what types of dates you are tracking within your requirements. Can you elaborate a bit more and provide any information on how this would help in eliminating your spreadsheets? Also, I did want to point out that you do have the ability to add custom fields (including date fields) to requirements. Thank you for the additional detail. In the meantime I will mark this unlikely to implement based on the workaround of adding custom fields, but we will re-evaluate as we understand this better. Thanks!