How do you structure your Aha! + JIRA Integration?


I am curious if anyone is using the new Aha! + Jira integration? We just launched it in December. The "2.0" integration creates a bidirectional link between Aha! and Jira, with custom options for linking the fields in both systems.

The enhanced framework now supports the following functionality:

  • Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type in Jira.
  • Map default or custom fields in Aha! to any “like” field in Jira and specify which direction the updates should flow (e.g. from Aha! or from Jira).
  • Automatically send outgoing changes from Aha! or choose to review and approve them.
  • Import records directly from Jira to make getting started in Aha! easy.

Has this update impacted how you structure your Aha!! + Jira integration? I imagine (and hope!) it helps solves some of the challenges discussed in this thread. Let us — and the Roadmap.com community — know what you think.

Full documentation and additional set up instructions can be found in these articles:

How did you start your first product management career?


I started my PM career when I was a software developer in a small 10 people team that functioned very much like a startup. We did not have a dedicated PM or tech sales. After we launched our beta, we had the opportunity to go on-site at a customer environment and demonstrate the product.  I volunteered for it, and did a pretty decent job. Since then, I was asked to participate in several on-site trials and demos. Every time I spoke to customers, i learned something new, and came back with ideas for our team. You can see where this is going. Ultimately I became the goto ‘PM’ for the team, and took this on on a full-time basis. Key takeaway - volunteer for opportunities to engage with customers. This is best done in a startup like environment where you don’t have dedicated PMs just yet.


I have coded when I was a software developer but I stopped doing that after I became a PM. The short answer is No. Product Management and Engineering are two sides of a coin - they compliment each other in creating the right product/features that drives sales. If you are coding than chances are you are not analyzing the market to determine who your target customer is and how you can stand out against competition, you are not talking to your target users/customers to understand their needs, and/or you are not helping engineers build the right features, in the right order of priority, with the right experience. Someone needs to do all the stuff that engineers can’t do. If you need more people to code then hire developers.

Any tips on how to revamp our existing product launch process?


Hi Ginny,

I definitely think the community can chime in and help here. But first, it would help if you share what your current process is. I know you stated it's a checklist, but understanding what you are currently doing and why you think it's not working will help us better answer your question and make recommendations.