Rally

When creating or updating a record in Rally set the rank of that record according to the corresponding rank in Aha!. This can be done using the rankAbove/rankBelow parameter using a similar technique that is used by the JIRA integration. Changes t...

While the current Aha! -> Rally integration does support Aha! creating a release with a release date in Rally when the initial send is made, any updates to the release date in Aha! are not updated in Rally. To be consistent with other integrati...

We recently made the update where we can populate a required custom field in Rally with a default value to facilitate the integration with required custom fields. This idea is to take it a step further and provide custom field integration mapping ...

Rally has a field for Completion %. The request is to be able to pull this data into Aha! features for visibility into the Completion %.

I understand the risks associated with automatically deleting from Aha! particularly when you initially setup your project -but if you insert a prompt (something like' would you like to delete the corresponding artifacts from Rally?") and allow th...

Rally may be configured with custom fields which are mandatory. Aha! should support populating these fields when creating stories or portfolio items in Rally.

Note: If you are using JIRA and have configured the integration, logged work is automatically updated by JIRA. If you have configured estimate association at the requirements level, logging time is also at that level.

If we already have User Stories in Rally that are duplicates of features in Aha! we want to be able to manually create a link between them.

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

Specific request is around WSJF value stored in AHA. Our team goes through activity of reviewing WSJF values and update AHA. The features in Rally also contain this field however this is not included when a feature is created. This would save time...