The pivotal integration only allows for 2-way integration only if originally pushed from aha initially. Even then it's pretty limited to status and description.
If I create an 'feature' in aha which maps to an 'epic' in pivotal, and someone adds a story for that epic in pivotal, then that story should be auto imported as a new requirement for the feature in aha. This is a very common use case since our dev teams will add technical stories for certain epics (features) and these will not be reflected in Aha.
Imported stories that we're previously in Pivotal, do not update in Aha when updated in pivotal
Comments do not link with stories or epics in any direction. Comments should sync 2-way for all epics and stories.
Two way integration with Pivotal Tracker should allow pre-existing Tracker stories to be associated with Aha! features/requirements etc.
In corresponding with Aha! support, Scott Goldblatt wrote:
You are correct in your observations that all Aha! integrations with issue tracking systems such as Pivotal Tracker are designed so that Aha! comes first in the process. The philosophy is...
Import epics/stories from existing Pivotal Tracker project
I want to import from Pivotal Tracker to Aha! and have it establish a link between my epics/stories in Pivotal to my Features/Requirements in Aha!. Right now I can import if I first export to a CSV. It would be easier to have a direct import capab...
about 9 years ago
Support Two Way Communication from Pivotal Tracker and Aha
Currently, Aha allows integration with Pivotal Tracker where you can create work in Aha and push that work into Tracker. Aha then keeps a constant status of the work/cards in play via Tracker. The integration works excellent until someone adds new...