We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requirements but we think it would be very benificial to be able to create To-Do's and link them to sub-tasks. This working method makes a lot of sense, especially if To-Do's could be linked to Requirments within Aha.
The current issue is that Aha recommends that we map Requirements to sub tasks, but this doesnt make logical sense to my development team - they feel that requirments should be requirments and that there should be a list of tasks associated with a requirement that works towards a complete feature.
|Release time frame|
Our recommended configuration for JIRA Agile users is to set the data objects up in a similar manner to how you have it (with exception to Requirements - as you've described).
While we can understand some discrepancies with the team, we feel that this set up allows for the greatest flexibility and has been reinforced from community feedback.
At this point, we do not have plans to allow To-do's to be integrated as this is a less flexible object and will not provide the capabilities available to requirements. Combined with current priorities, it is unlikely that we implement this in the near term. We hope you can understand.