RELATED IDEAS
"Real" 2-way integration with pivotal
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.
- Deletion of epics and features do not sync.
| Release time frame | 6 months |
12
MERGED
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...
1
Future consideration
37
MERGED
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...
8
Future consideration
8
MERGED
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...
0
Future consideration
Are there any further updates on this?
Due to the very long window between first request and potential implementation, we've moved away from trying to leverage the integration feature.
Hi Trevor, the updates referenced in the admin response on this idea have not yet been implemented for Pivotal Tracker. There are still significant updates to come.
I noticed a post updated on April 12th, 2018 for this feature: https://support.aha.io/hc/en-us/articles/202001007-Integrate-with-Pivotal-Tracker-two-way-
I there more coming in development, or is this final state?
Agreed, this would make Aha viable in our shop!
This would be essential for us to allow us to work with our devs in one platform (Pivotal) and many other folks in Aha!.
Yes please. As previous described, the dev teams do a lot of work in Tracker changing and adding stories such as NFR's, architecutral etc. during sprint planning. To get the best out of Aha, these need to be pushed over.
Bought AHA monthly license yesterday, before realizing this limitation. If there is no action taken or scheduled on this issue, I will likely cancel my subscription as this is a deal breaker.
I wholeheartedly agree with Marco N.'s comments below
yes!!!!!! we need this
In corresponding with Aha! support, Scott Goldblatt wrote:
and it was suggested that I follow up with an idea, and I've found this one here.
Here's what I wrote:
It's true that the Product Manager does a lot of initial work in Aha!. But there's an awful lot of give and take when the stories reach the engineering team. We move stories around, we change them, split them into multiple stories, etc. etc.
Much of that work happens in meetings, where PM and Engineering review the stories in Pivotal Tracker together.
It's unlikely that any PM is going to have the discipline to also have Aha! open. It's unrealistic that the PM would stop the flow of discussion, laboriously make those changes in Aha!, send to PivotalTracker, then make sure Tracker refreshes and reflects the changes, before resuming the discussion.
I do think it's realistic for the PM to (sometimes after the fact) annotate the changes made in Tracker with Aha! IDs. That way, Aha! would be updated per the results of the meeting. It doesn't have to be automatic, but the fact that stories _must_ be created in Aha! in order to be tracked by Aha! is a big drawback.
We have several meetings per week. Pivotal Tracker's designed to be very dynamic, precisely so that we can make changes in real-time as we discuss.
Importing data only solves this problem for things that have transpired in the past. Without "true" two-way integration, it'll be a lot harder to make use of the PT integration.
I'm trying to take advantage of Aha! while working with several years' worth of stories in Tracker, so I'm marking this Idea as, "I need it... Yesterday"
How does this not have more votes!? Yes please!! Would even pay money for it.
Agree with everyone else. Let's get the sync right with Pivot Tracker. Don't understand why this has not been completed.
This is a must have. Another helpful aspect of the integration would be to carry over release dates from Aha! and convert to milestones in Tracker.
We will most likely cancel our sub in a month because of not having this REAL integration. Our dev team routinely writes new stories, and I would love to just get an AHA ID to plug in them and it sends all the info back to Aha. AND real updates in PT should go to Aha.
We need this. Why has Aha! not implemented this yet? What would it take to get this on the roadmap? It is a reason we are debating leaving Aha!
This perfectly describes the main reason we have not elected to sign on with Aha! at this time.
This perfectly describes the main reason we have not elected to sign on with Aha! at this time.
Definitely need this soon
Yes please!! It would be great if we could create stories in PT and they flowed back into Aha.