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 add...
Tags should propagate bidirectionally into Pivotal Tracker
Much like status, it would be nice if tags on features would propagate instantly to stories in PT bidirectionally. We have historically used PT labels to organize aspects of our sprint. It would be nice to setup initial tags in Aha and have those ...
Aha! has a cool new functionality of exporting pivots as interactive webpages, where users can click on certain elements (epics/features) and show more details. This is very useful for communicating with commercial teams. The only limitation is th...
We are currently using the Aha.io and pivotal tracker integration to help seed our product roadmap into the engineering team's workflow. This has been great so far but the one biggest points of friction is trying to keep track of the features that...
about 9 years ago
in Pivotal Tracker
Synchronisation of the owner field. Stories created in Pivotal Tracker should have the corresponding owner on the Pivotal Tracker side. That can be determined based on e-mail, your team confirmed that it is possible. Priority 2 of 4
It would be helpful if one of the mapping options with Pivotal Tracker could include the following options:
Master Feature to Epic
Feature to Story
Requirement to Task
Instead, the only option for mapping to Epics in PT is to use Initiativ...
It would be very nice to setup our pivotal tracker integration on a product line. That way if a ticket moves between products in that product line it retains the integration that was configured for it.
It doesn't have to be fancy -- they could just be added to the feature description.
We collect substantial extra information in our idea portal in the form of custom fields -- severity, customer mood, steps to reproduce, examples -- and it would ...