Just Launched! — Sync Feature Dependencies Between Aha! and Jira

There are two kinds of surprises at work. There are the welcome ones, such as when you learn that your teammate completed a critical work item ahead of schedule. But there are also not-so-delightful surprises, like when your engineering team discovers a technical blocker during development. Unknown dependencies like that can put your big plans at risk. 

You can now map record links in Aha! with issue links in Jira  — so dependencies are instantly visible across both systems.

If you already use our integration with Jira, then you know it is possible to link Aha! records (specifically, initiatives, features, master features, and requirements) with issues in Jira and map nearly any “like” fields between systems. Previously, syncing dependencies between systems was not possible. 

With today’s enhancement, you have an option to bi-directionally map Aha! record links with Jira issue links. This means you can identify relationships (such as relates to, depends on, duplicates, impacts, and blocks) between work in either system and the information will instantly be available in both.

Here is how you can enable this in your account:

Map dependency fields
Create a field mapping between the record links field in Aha! and the issue links field in Jira. Then configure to map link types between systems. In the example below, we are connecting feature record links in Aha! with story issue links in Jira. You must be a workspace owner in Aha! to create new integrations and modify existing ones.

The new field mapping is available for initiatives, releases, master features, and features.

Automatically sync dependencies
After you update the integration, dependencies will automatically update for everyone to see in both tools. This way, engineering understands how feature dependencies impact your roadmap and you are instantly informed of any issues that could derail your release or launch plans. 

Visualize dependencies in Aha!
See dependencies in the record links section of the drawer view.

Now you can work even more closely with engineering to deliver features on schedule.

These new field mappings will help you work even more efficiently. And the next time engineering discovers a dependency that could impact what you have planned — you will instantly know. 

Sign up for a free Aha! trial — be happy

The enhanced Jira integration is 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 build and market lovable products. 

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.

About Claire and Aha!

Claire is passionate about helping product and marketing managers set brilliant strategy and deliver results. She is the Group Manager, Product Marketing at Aha! — the world’s #1 roadmap software. Claire has more than 15 years of marketing and software experience. Previously, she led product marketing at an agile-based work management platform.

Sign up for a free trial of Aha! and see why more than 300,000 users worldwide trust Aha! to build products customers love.

We are rapidly growing and hiring!

  • Customer Success Managers (product manager experience required)
  • Product Marketing Managers
  • UX Designers
  • Rails Developers

Work from anywhere and be happy. Learn about our team — see current openings.

Comments

  1. Scott

    The Linked Issues field is not available in my Jira integration mappings. Is there something I need to change in Jira?

    Reply
    1. Claire George Post author

      Hi Scott — thanks for your question. You might need to click the “Reload configuration” button to see the latest Jira settings. If that doesn’t solve it for you, please contact our Customer Success team at support@aha.io so we can take a deeper look.

  2. John

    My group is all about linking these 2 systems together to benefit both product management and engineering teams simultaneously. However, we’re struggling to find a balance between daily value and long-term maintainability. As the Jira Admin for our engineering teams, how can we avoid the need to create a new “project” in Jira for every new product managed through Aha? Many of our projects are only weeks or months long and not worth setting up all these as separate products in Jira to support Aha integrations. Is there a way to configure Aha to scope individual products by Jira component if all Jira projects are managed in a single Jira bucket?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *