Just Launched! — Enhanced Aha! + Jira Integration for Agile Sprint Planning

Many of you rely on our enhanced integration with Jira to keep information flowing smoothly between product and engineering teams. And many of your engineering teams use Jira for agile sprint planning. Well, we have good news — you can now sync features in Aha! with sprints in Jira. 

With this update, you now have the ability to coordinate sprint plans — this will help both teams work together closely to build great products.

If you have been waiting for our 2.0 integration with Jira to support this functionality before setting it up, now is the perfect time to make the transition. Note that only administrators in Aha! can create the custom sprint field needed to sync sprints. Product owners can modify integration settings. Product owners and contributors can update features with sprint information and send them to Jira.

Follow these steps to automatically sync sprints between Aha! and Jira:

  • Create a custom field to capture sprint information in Aha! within a tags field or editable choice list.
  • Modify your Jira project settings in Aha! to select a corresponding Jira board. This is necessary to send sprint information from Aha! to Jira. Note that you can receive sprint information from multiple Jira boards.
  • Update your integration field mappings to link your new custom sprint field with the sprint field in Jira.
  • Click the Update records button in your integration settings to pull in the current sprint information from Jira.

Coordinate sprints between both systems
You can group features into sprints in Aha! and send the information to Jira. Or you can plan sprints in Jira and immediately see the same information in Aha!
 The bi-directional integration keeps everyone in sync, even as plans change.Customize feature cards in Aha! to make the sprint details immediately visible.

Track sprints in roadmaps and reports
For example, you can create a pivot report to track the progress of features by sprint during development. Then, add the report to an Aha! notebook and share it with the team. This makes it easy to communicate release updates with others. 
Easily include the custom sprint field in list reports, pivot tables, and roadmaps.

Go ahead and sync your features in Aha! with sprints in Jira. The additional level of visibility will help your team move even faster.

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 200,000 users trust Aha! to set product strategy, create visual roadmaps, and prioritize releases and features.

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 Jessica and Aha!

Jessica is passionate about showing product managers there is a better way. She is the Product Marketing Manager at Aha! - the world’s #1 product roadmap software. Previously she led product at YouEarnedIt, a top five employee engagement platform. Before that she was a product marketing manager at several business-to-business SaaS companies.

Sign up for a free trial of Aha! and see why 200,000 users at the world’s leading product and engineering teams trust Aha! to build brilliant product strategy and visual roadmaps.

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. Björn

    Seems to be a great feature though I’d rather sync my aha-releases to JIRA-sprints since every sprint is a release for us.
    I tried to follow the instructions but cannot add a mapping between my newly added custom field “sprint” to a JIRA field of that type. (It’s an existing mapping.) The JIRA list simply doesn’t show a sprint field. I, therefore, can’t choose a JIRA board, either. Are there any more preconditions that should be met before trying to configure the mapping?

    Reply
    1. Eva

      I agree. every sprint is a release for us to. I want to show what features were completed in that sprint release.
      I like Aha releases and how its displayed on the feature board as I can move those cards around from sprint to sprint or parking lot as part of planning for the overall project/epic/master feature.
      This custom field is not ideal and wont be used sorry.

    2. Jessica Groff Post author

      Hi Björn,

      Thanks for the note. Please send a note to us at support@aha.io. We may need to schedule a screen share to see your configuration, but our customer success team of former product managers will be happy to help with why that sprint field is not currently showing up.

Leave a Reply

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