ADD A NEW IDEA

FILTER BY CATEGORY

Pivotal Tracker

Showing 12 of 6678

"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...
Guest over 5 years ago in Pivotal Tracker 23 Future consideration

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 thos...
Jason Novek about 5 years ago in Pivotal Tracker 1 Future consideration

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...
Suzanne Vaughan almost 6 years ago in Pivotal Tracker 4 Future consideration

Sync owner field from Aha! to 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
Guest about 6 years ago in Pivotal Tracker 2 Future consideration

Sync comments between aha features and pivotal tracker.

This would mean that our dev team and product managers can use a common discussion forum between the systems.
Guest over 5 years ago in Pivotal Tracker 1 Future consideration

Pivotal Tracker Integration Mapping

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...
Tom Beck about 2 years ago in Pivotal Tracker 1 Future consideration

Custom fields should propagate to Pivotal Tracker

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 ...
Jason Novek about 5 years ago in Pivotal Tracker 2 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 5 years ago in Pivotal Tracker 0 Future consideration

Track dependencies in Pivotal Tracker using Blockers

How this would work: If an Aha ticket has "depends on" links Add the Pivotal Tracker ID for each Depended on ticket in AHA that has already been pushed to Pivotal Tracker blocker sections See PT API document here:https://www.pivotaltracker.com/hel...
Kelly Kampen over 3 years ago in Pivotal Tracker 0 Future consideration

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 ...
Stephen Hughes over 4 years ago in Pivotal Tracker 1 Future consideration