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...
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...
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...
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 ...
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.
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 -&g...
It would be very nice to setup our pivotal tracker integration on a product line. That way if a ticket moves between products in that product line it retains the integration that was configured for it.
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...