On some occasions we will end up with multiple JIRA tickets for the same item in AHA. We'd like to be able to track each of these in Aha, but most importantly be able to pull the time tracking data into aha across all of the tickets.
Addition to this, we could have one main ticket that Aha is updating, but multiple tickets that are linked and time data is pulled from. Any updates in Aha only go to the primary ticket\jira item.
Matt - Couldn't you just house the main Aha ticket and then create separate Requirements for Subtasks in Jira?
Seems like the structure of what your are doing could easily be accomplished with the current setup of the tool?
Addition to this, we could have one main ticket that Aha is updating, but multiple tickets that are linked and time data is pulled from. Any updates in Aha only go to the primary ticket\jira item.