RELATED IDEAS
Add an "Import from Rally" utility for uploading the Rally backlog into Aha!
Add an "Import from Rally" utility for importing existing features, user stories, etc. and supporting metadata into Aha! as Features and Requirements and creating corresponding links between the data objects in support of the bi-directional integration for ongoing updates.
-
ADMIN RESPONSEDec 18, 2017
We have launched an enhanced Rally integration. This integration will allow you to import new and existing records from Rally, along with several other new capabilities including the ability to:
- Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
- Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Rally)
- Automatically send outgoing changes from Aha! or choose to review and approve them
- Import records directly from Rally to make getting started in Aha! easy
Check out the blog post for more details.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
That is great news – can’t wait to try it out!
Import from Rally is coming very soon - in about two weeks.
Is there an ETA on this one?
Any updates
any update?
I have wanted this for a long time - would be very helpful to have 2-way synch.
I'm not convinced that user stories should be in Aha!. Aha! should be reserved for high-level planning. Once we get down to the User Story level then everyone should just use Agile Central directly. What's the point of having two separate systems with the exact same data?
Is this on the Rally integration road map? Also, are Rally integration enhancements' road map available for your Clients? If so, Optum would like to see it? If not, why not?
We have a couple different related scenarios where this functionality would provide benefit. We have existing projects that are in Rally and want to begin using AHA. There's a lot of time and effort invested in the content in the features/user stories in Rally and need the ability to import them into AHA.
Additionally, there are scenarios where during planning a feature delivery and execution we may have to create additional user stories. These actions are generally done during or post planning and the creation can be done by a user that doesn't have access to AHA but does have access to Rally. The completion of these stories are generally required to consider the feature complete. If these don't make there way back to AHA then the picture of complete vs. still in progress is only partial if we don't have a way to import these back to AHA.
Yes please implement this as it would save the double data entry since most of my backlog is in Rally. Right now not really using AHA because of this limitation.
The way I see it, this is the single most important update to allow all the companies currently using Rally to implement Aha!.
I would also love to see User stories from Rally get back to Aha as requirements
This is huge. We have an active development group that creates many stories in Rally (which is good), but it takes these stories out of the Aha picture. I can only have Aha/Rally sync for features created in Aha and pushed to Rally. It would be fantastic to be able to have Aha link to existing Rally artifacts.
We CAN import from existing stories from Rally, but there is not any two-way sync option for features created this way.