"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.
  • Guest
  • Feb 5 2015
  • Future consideration
Release time frame 6 months
  • Attach files
  • Dirk Kelly commented
    4 Sep, 2019 11:44am

    Are there any further updates on this?

  • Marco N. commented
    4 May, 2018 10:01pm

    Due to the very long window between first request and potential implementation, we've moved away from trying to leverage the integration feature.

  • Admin
    Austin Merritt commented
    4 May, 2018 09:51pm

    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.

  • Trevor Nelson commented
    4 May, 2018 04:40pm

    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?

  • Luke Macfarlan commented
    16 Jan, 2018 02:21pm

    Agreed, this would make Aha viable in our shop!

  • Fernando Medina Corey commented
    9 Oct, 2017 09:39pm

    This would be essential for us to allow us to work with our devs in one platform (Pivotal) and many other folks in Aha!. 

  • Guest commented
    29 Jun, 2017 08:43am

    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.

  • Admin
    Ron Yang commented
    17 Mar, 2017 02:48am
    Thanks for the continued feedback and support for this idea. We currently have a team actively working on a significant upgrade to our integrations framework. Our goal is to bring all of our integrations closer to feature parity and to support more flexible configurations. The idea that is being discussed here will be included in this upgrade. 

    We plan on delivering the new framework during Q2 and a rolling wave of improvements to our existing integrations starting in the same timeframe. It is a major undertaking and we appreciate your patience.
  • Brian Pino commented
    16 Mar, 2017 10:52pm

    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

  • BETTY SAPONAR commented
    16 Jan, 2017 10:37pm

    yes!!!!!! we need this

  • Marco N. commented
    6 Jan, 2017 05:07am

    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 that PM's own the backlog and do all their initial grooming, prioritizing, and planning in Aha! When ready, they then send to Engineering and their tool of choice to manage the How - how those plans are best executed. 

    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"

  • Matthew O'Neill commented
    28 Sep, 2016 09:58am

    How does this not have more votes!? Yes please!! Would even pay money for it.

  • Kenny Lee commented
    23 May, 2016 03:24am

    Agree with everyone else.  Let's get the sync right with Pivot Tracker.  Don't understand why this has not been completed.

  • Iam Williams commented
    22 Feb, 2016 01:46am

    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.

  • Justin DuBois commented
    21 Jan, 2016 07:21pm

    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.

  • Sean Kester commented
    19 Dec, 2015 09:11pm

    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!

  • rob collyer commented
    27 May, 2015 01:32pm

    This perfectly describes the main reason we have not elected to sign on with Aha! at this time.  

  • Boyd Tracy commented
    26 May, 2015 01:59pm

    This perfectly describes the main reason we have not elected to sign on with Aha! at this time.  

  • Adam Jackson commented
    18 May, 2015 07:08pm

    Definitely need this soon

  • Mike Gullo commented
    1 May, 2015 08:17pm

    Yes please!! It would be great if we could create stories in PT and they flowed back into Aha.  

  • Load older comments
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e