Pivotal Tracker: Send releases to PT

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 hit the backlog and understanding which release they are tied to during sprint planning.

After playing with both products it turns out that epics in pivotal tracker are pretty much a 1 to 1 correlation to releases in AHA. Essentially they are a grouping of features which all live under a overall goal (what is shipped to users). It would be amazing that if you could send a release to pivotal tracker which in turn creates an epic that is tied to it. (and possibly push over all the underlying features and tag the epic on them.

I am up in the air if pushing features over automatically is the best approach as there may be features in aha that aren't engineering team specific.

The workflow in my head works like this:

1.) Send Release to Pivotal Tracker

2.) AHA creates the Epic with the name of the release in pivotal tracker and attaches the epic id to the release in AHA.

3.) Any subsequent features within the release i send to pivotal tracker would tag the epic.

You guys have built a great product and so far it has been awesome, this would help our and I am guessing others that use pivotal tracker's workflow immensely and would help with the fragmentation that exists when switching between systems.

  • Suzanne Vaughan
  • Nov 14 2014
  • Likely to implement
Release time frame
  • Attach files
  • Mike Gullo commented
    May 1, 2015 20:15

    Yes please.  I've been using initiatives as a work around, but it's an extra few steps.

  • Frank Frenzel commented
    July 28, 2015 15:27

    This would be a terrific value add to our process as well

  • Eric Taylor commented
    February 18, 2016 08:46

    I third the motion...

  • Daniel Leibu commented
    October 26, 2016 13:30

    I agree with Suzanne's underlying idea which is to reflect Aha! releases in Pivotal. I am not sure that doing so with Pivotal Epics is the best approach. I would suggest using Release markers instead.