ADD A NEW IDEA

Pivotal Tracker

Showing 19

Link Aha! feature to an already existing pivotal story

It would benefit users who are trying to clean up a project that already exists. There may be information captured in pivotal that would be time-consuming to replicate.
Guest almost 6 years ago in Pivotal Tracker 1 Future consideration

When I move a feature to the parking lot in Aha, it should move to the icebox if it exists in Pivotal

Most sprints priorities will change a little bit as time goes on and it will be appropriate to remove a ticket that was added previously. Likewise, if a sprint is over subscribed some tickets may roll over into the next sprint. When this happens, ...
Jason Novek about 9 years ago in Pivotal Tracker 0 Will not implement

When sending a Release to Pivotal Tracker, items are added to the backlog in reverse order

Items are prioritized in Aha's release area by the Product Manager. When sending the release to Pivotal Tracker, the Stories that appear in PT are in reverse order, meaning the engineering team must spend time comparing lists to fix the order. I e...
Guest over 8 years ago in Pivotal Tracker 1 Will not implement

Features should Inherit initiatives from Release & Master Release so all Pivotal stories are under the Epic after sending to PT (and the Epic is actually created)

When pushing a feature to Pivotal Tracker, a user can select a mapping that allows for initiatives to be mapped to epics. The only initiatives this works for are initiatives directly referenced by a Feature. Any initiatives referenced by the Relea...
Guest about 9 years ago in Pivotal Tracker 7 Unlikely to implement

Pivotal Tracker: 2 way sync for Requirements — not just Features

Today PT can only update status in Aha for Features. We'd like to have it update the status of requirements as well. In our case, it's particularly useful because we map Aha Features to PT Epics (and Aha Requirements to PT Stories). So we're blin...
Yok Tan almost 10 years ago in Pivotal Tracker 2 Already exists

Pivotal Stories added to Epics converted to Requirements in Features

The Pivotal integration is good, but fails to capture a common case for us. Our teams often add new Stories to Epics that are essentially Requirements on the corresponding Feature. We track progress through these Stories/Requirements. Right now, t...
Christopher M over 3 years ago in Pivotal Tracker 0 Future consideration

Sending Feature to Pivotal Tracker should send story point Estimate

When Story Points are added to a story in PT, they are updated in Aha. This is great. However, it would also be nice if the Feature estimate in Aha (if specified in Story Points) was also sent to PT when the feature is pushed using the Action ->...
Guest over 8 years ago in Pivotal Tracker 0 Already exists

Ability to Create Integration Templates for Pivotal Tracker

The integration templates for Jira have saved me TONS of time. I would love the ability to lean on templates for all of my Pivotal Tracker integrations as well.
Guest over 6 years ago in Pivotal Tracker 0 Will not implement

One Product, Multiple Projects in Pivotal Tracker

A lot of our features have multiple components that correspond to different projects in Pivotal Tracker. Right now I can only sync my product with a single project in PT, which means I don't get to take much advantage of the integration. I keep a...
Guest over 8 years ago in Pivotal Tracker 1 Already exists