RELATED IDEAS
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 Release (or Master Release) that feature has been assigned are ignored.
-
ADMIN RESPONSEMar 11, 2016
We currently have the capability to link strategic initiatives to both releases and features. A common use case is that while the general strategic theme for a release may be linked to a specific initiative, you may have features which link to and span across multiple initiatives.
At this time, we do not have plans to make updates in this area due to community feedback and current priorities. We hope you can understand.
© 2024 Aha! Labs Inc.•All rights reserved
I also love this suggestion. In fact, the initiative -> epic PT integration was really unclear until I read this thread and realized it only created epics for initiatives tied directly to tasks. I created a release which was tied to an initiative and couldn't figure out why the pivotal tickets were not associated with the epic.
Alongside that - do I always need to click "Update Pivotal Ticket" whenever I add a feature to an initiative? This integration is a great start but seems a bit half-baked.
My apologies Suzanne, I did not notice you had already modified the title and read it as you suggesting I modify it. All set, thanks.
Hi Frank - you cannot modify it. I can because I am an Aha! user for our account. Is there something you want me to edit?
Thanks for the feedback Suzzane.
I don't seem to be able to modify the Idea title from my view (unless I am missing something).
Ah! I think what threw me off is the "when creating pivotal stories". If you don't mind, I will modify the title a tiny bit.
Hi Suzanne,
Not sure we are on the same page. What I am suggesting is that for a release that has been tied to an Initiative, that has then been loaded with features, I would like the option to inherit the Initiative for all Features of my release when I send them to pivotal tracker.
Right now, for an initiative to create an epic, it needs to be associated at the Feature level. Initiatives tracked at the Release level are ignored when sending to pivotal.
Hi Frank -- the reason we don't send Initiatives over unless a feature is attached is because epics contain stories. If no stories exist, it's typically premature to create an epic. Once the stories are created and you update to Pivotal Tracker, the epic will be created. Can you help us understand why you'd want an epic created prior to it being worked on?