RELATED IDEAS
Enhance two-way sync with Rally to support Rally -> Aha!
Features are created in Aha! and then pushed to Rally. User Stories (US) are created in Rally and associated to the Features. These associated User Stories should be synced back to Aha! and associated with their respective Features as Requirements
-
ADMIN RESPONSEJan 18, 2018
We have launched an enhanced Rally integration. This integration enhances the two-way sync, 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
Tracy, the Aha! to Rally integration already supports synchronizing user stories from aha! to Rally. With the Integrations 2.0 updates it will also be easy to import stories from Rally to Aha! when they are created in Rally.
Not all users of AHA! are users of Rally, therefore, integrating user stories between the two apps would be extremely helpful
any updates?
I agree with the suggestion of enhancing the two way sync with Rally. in theory we should probably create most, if not all, backlog items in Aha and funnel those down to Rally. in reality there are times where the team needs to 'split a story' or 'create a new story under an already established feature', in cases like this Rally should be able to to communicate that item back up to Aha.
any updates?
Any updates?
Another critical enhancement is the estimate field two way sync.
Link to the % complete of a feature in Rally which is calculcated within rally based on the number of items below it.
Greatly, greatly needed. Too many changes happen in Rally that then need to be manually added to Aha!.
This doesn't seem like a good idea. 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?
This is key to Aha's success within Optum. When will this be implemented?
Our team ran into this today:
the issue that happens when Scrum team tries to split a user story in Rally. Essentially, Aha can’t see a story unless Aha generates it; we need Aha to be able to see a story that gets added, in Rally, to an Aha-originated feature.
This would be useful for us
Scrum teams could use this functionality to split stories--would be helpful and less disruptive to let them do it from Rally
It is important to our organization that scrum teams are adding/editing user stories within Rally. Lack of 2-way integration of the requirement/user story will limit the rollout of Aha! within our organization.