Like many other users, we map features to tasks and requirements as sub-tasks in our integration. For us it logically makes sense that JIRA Epics are therefore bound to releases (as tasks sit under Epics, and features sit under releases) - we use initiates as 'themes' that may have a number of releases added to them over time.
It doesn't appear as if this is supported in the Aha! JIRA integration, and when I create tasks within an epic in JIRA, and link them to 'features' in Aha! (telling Aha! to inherit all details from JIRA) for some reason it completely removes the task from the epic when I go back into JIRA and makes it an orphan task in JIRA, no longer associated to the epic it was originally created in.
|Release time frame|
We have launched an enhanced Jira integration. This integration will allow you to map Aha! releases to various issue types in Jira including epics, along with several other new capabilities including the ability to: