Integrate with Rally - CA Agile Central (integrations 2.0)

This support article refers to the 2.0 version of the Aha! Rally integration. For the 1.0 version, please reference this document.

Aha! provides a two-way integration with Rally that allows product teams to send their planned work from Aha! to their development team working in Rally. Before configuring any integration for the first time, it is important to fully understand how to think about integrating Aha! with your development tool.

This integration supports sending the following Aha! records to Rally:

  • Initiatives
  • Releases
  • Master features
  • Features
  • Requirements

The above Aha! records can be mapped to the following Rally records:

  • User stories
  • Portfolio items
  • Releases

Configuration

To set up an integration with Rally, you need to be a Product Owner in Aha! for the product you wish to integrate. You will also need to have a Rally account that has proper access to create/edit records in Rally for the project you plan to integrate with.

1. Navigate to "Settings > Product" and press the "+" next to "Integrations" on the left side navigation bar. Select "Rally" from the integrations 2.0 grouping.

2. This will launch the integration configuration wizard. The first step is to name your integration and optionally select a template if you have already created one. Click "Save and continue."

Integration_setup_page_1.png

3. Next, you will be prompted to authenticate. Aha! uses OAuth 2.0 for authentication, and if you are already logged into an active Rally session in your browser, you will not be prompted for credentials. If you are not currently logged into Rally, you will be prompted with a Rally authentication screen.

4. After authenticating, you will be prompted to choose a workspace. The list of workspaces is based on what your Rally user has available to them.

5. After selecting a workspace, you will be prompted to chose which project in Rally you wish to integrate with. Similar to the workspace selection, the list presents the projects that you have access to within the previously selected workspace.

6. Next comes record mappings. This step allows you to configure how Aha! records are mapped to your Rally records. The default mappings are based on what is most widely used across our customers. However, you are free to remove the default mappings and add your own to map records together based on what makes sense for your team and how you work.

Aha-Rally-Integration-Mappings.png

7. Within record mappings, you have the option to also specify your field mappings. This is an advanced option within the configuration that allows you to customize how each field within the record is mapped between Aha! and Rally — as well as what relationship links exist for those records.

The relationship links are important to understand because they establish the ability for records created in your development system to be automatically imported into Aha! in certain use cases. You can learn more about them here.

Aha-Rally-Field-Mappings.png

8. While not every user will need to customize their field mapping, you do need to define the way statuses are mapped. Within the field mapping section for each Aha! record, there is a line for "Status" with a gear icon at the far right. Click the gear icon to open up the status mapping window.

Aha-Rally-Status-Mapping.png

9. When mapping statuses, you will be presented with your Aha! status workflow for the record type on the left and your integrated system status workflow on the right. You can drag-and-drop the statuses to create groupings and mappings. In the above screenshot, you can see that multiple statuses have been grouped together where the Rally statuses of "Measuring" and "Developing" are mapped to the single Aha! status of "In development."

10. With your records, optional field mappings, and statuses defined, you can click "Save and continue" to move onto the last step in the workflow. The "Enable" step allows you to specify how updates from Aha! are sent to your development system. The default is for the user to approve outgoing changes. We recommend this option until the team is familiar with how the integration works, at which point you can switch to the automatic sending of changes. The approval step allows teams that are new to the integration to validate what is being sent to their development system, which can help prevent unintentional changes from going through.

 

Enable_integration.png

11. Finally, test the integration by opening one of your features in Aha! and use the "Actions" drop-down to select "Send to Rally." You should see a link to the created Rally record appear on the Aha! feature after a few seconds. This will let you easily click into Rally to verify that everything was sent through correctly.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Roadmap software to manage your products.
Finally, connect strategy to execution.

Powered by Zendesk