JIRA is the tracker for teams planning and building great products. Thousands of teams choose JIRA to capture and organize issues, assign work, and follow team activity. At your desk or on the go with the new mobile interface, JIRA helps your team get the job done.
Do your planning in Aha! and then move your initiatives, features, requirements, attachments, tags, and estimates into JIRA with no hassle. As work gets done in JIRA, updates flow back to Aha! to keep you in the know. You decide how you want to map initiatives, features, and requirements from Aha! to JIRA. It's common to have them be epics, stories, and sub-tasks. But, it's totally up to you.
When a release is first sent from Aha! to JIRA a corresponding version record will be created. This makes it easy to think about market-impacting releases in Aha! and do sprint planning and engineering management in JIRA.
You need to be a Product Owner in Aha! and an Administrator in JIRA to set up this integration. Please carefully follow these instructions to ensure that the integration is properly configured. There are two steps to this integration and both must be completed. If you are using the on-premise version of JIRA, you will need to create a firewall exception: see the IP Whitelist doc article for help.
Note: You can add the integration multiple times if you want to integrate multiple JIRA projects with a single Aha! product.
This will enable changes in JIRA to be reflected in Aha! and make the integration two-way.
Note: Only one webhook should be created per Aha! account. All subsequent integrations will be two-way automatically.
Once you have added the JIRA integration, you can directly import your feature backlog with the import from JIRA functionality.