Just Launched! — Keep Features in Sync as They Move Across Projects in Jira or Rally
Thousands of product teams rely on our integrations with Jira and Rally to build product and track engineering progress. We just created a better way to keep records in sync when they move across projects in your development system — so information flows even more smoothly between Aha! and those tools.
Integrated features now remain synced between Aha! and Jira or Rally as they move across projects in the dev system.
If you already use our integrations with Jira and Rally, you know it is possible to connect a product in Aha! with one or more projects in those systems. This means, for example, if your development teams use different projects to manage their work, you can set up multiple integrations to send features from Aha! to the right place.
But after records are sent from Aha! to the development tool, those features are often moved around by the engineering team as work is assigned. Previously, when integrated features were moved across projects in Jira or Rally, they would no longer stay in sync with Aha! — which meant you had to manually reconnect each record to send and receive updates.
Now, when records that have been created in Aha! and sent via the integration are moved across different projects in the development system, the corresponding record in Aha! stays up to date. Please note that to benefit from this new functionality, you will need to make sure your integrations use the same template. You must be a product owner in Aha! to create new integrations and modify existing ones.
Here is how to start using this enhancement:
Set up your integrations — the same way
Create integrations between a product in Aha! and multiple project spaces in Jira or Rally using the same template. Make sure the “Based on template” box is checked in the mappings step of your integration settings. This keeps your record and field mappings consistent when records move across projects.
The integration link will also be maintained when you move records across Aha! products — as long as the products share the same integration template.
Keep records in sync across projects
When you send Aha! records (such as master features, features, and requirements) to your development system, engineering can distribute the work across projects and you are automatically informed of updates. This is especially helpful if your development manager uses a project in Jira or Rally to centrally manage epics and then assigns child stories across projects for the team to implement.
When features move to a different project in your development tool, the record link is automatically updated in Aha!
Go ahead and let engineering decide where features belong in Jira or Rally — without worrying about missing updates.
To benefit from the new functionality, you will need to utilize the 2.0 integration for Jira or Rally. If you have not yet done so, you can convert your existing integration from 1.0 to 2.0.
Sign up for a free Aha! trial — be happy
Jira and Rally and over 25 more integrations are available to all Aha! customers. If you are not already an Aha! customer, you may want to sign up for a free 30-day trial or join a live demo to see why more than 250,000 users trust Aha! to set brilliant strategy, capture customer ideas, create visual roadmaps, and manage breakthrough marketing programs.
Aha! is a trademark of Aha! Labs Inc. All other company and product names may be trademarks of the respective companies with which they are associated.