The current integration with Rally provides the ability to plan releases and vet and prioritize the features before sending to Rally development. This is very helpful because only those features that should have focus are sent to development. It would be beneficial to have automatic status updates from Rally back to Aha!.
Currently Rally does not have an API that allows this two-way functionality. Aha! will add two way support to the integration as soon as Rally makes webhook support available.
How to get updates back to Aha!
All features can be updated using the universal import capabilities in Aha! under Settings -> Product. Simply export a CSV file from Rally once a week (or on some regular cadence). Ensure you include the Aha! Feature reference ID and the status. Then import into Aha!. This will update all of the features. See Update features using Import from CSV for more help.
Our projects are synched between Rally and Aha to a degree. In Aha you have to manually push your changes down to Rally via a dropdown selection. Once you have established the link between Aha and Rally, Rally updates will automatically be sent to Aha. Unfortunately, you have to always push your Aha updates to Rally.
You can define the mapping of fields and statuses between Rally and Aha in Aha's Product/Integrations settings.
Also there should be a way to migrate the current rally features to aha! so they are linked
Two way sync now works with Rally. There are some more details in the release notes here: http://support.aha.io/hc/en-us/articles/208090623-Release-Notes-through-2016-02-26
In order to take advantage of the two way sync with an existing integration, making any configuration change to the integration will automatically install the webhook in Rally.
I see the status of this idea is "Shipped". What does "shipped" mean in this case?
or
Waiting on the Aha/Rally Integration. Any status updates on this?
Working to buy Aha but Management is having a difficult time as one of our company objectives is for every department to be "agile" and use Rally as a source. Aha not receiving automatic status updates is a critical pain point.
While the universal import could be used to refresh Rally status, it is critical that the Rally user story include the Aha Feature Reference ID when the features/requirements are pushed to Rally. There should be a way to map this to a custom Rally field.
We would need this too