1,021,678 is a big number. And it represents a lot of work. As of today, that is the total number of requirements you have created in Aha! — do the math and it’s roughly one new requirement every two minutes since we launched in 2013. Product managers around the world have been busy.
Crisp and concise requirements are what make it possible to provide clear direction to the engineering team. You took the time to write more than a million requirements, so we want to make sure your engineers have easy access to that information.
Today, we give you the ability to sync custom fields on Requirements with one of the most popular integrations in our partner ecosystem — Atlassian JIRA.
You can use custom fields in Aha! to capture specific details such as acceptance criteria, priority, and technology components — then send them to your engineering team. This gives engineers the details they need to better understand what is being requested and why it matters.
Here is how it works:
Describe exactly what customers want
First, define your features and requirements in Aha! Use custom fields on Requirements to capture data that is important to your business but not a part of the application by default. For example, you can use a custom Note field for “Acceptance criteria” to communicate to engineering exactly what the new functionality should accomplish.Customize requirements to include the details your engineering team needs.
Communicate requirement details to engineering
Communicate details to engineering by selecting Send to JIRA from the Actions menu on a feature. This two-way integration on custom fields allows both you and your engineers to automatically send updates between Aha! and JIRA.
Custom fields in Aha! are automatically sent to and from JIRA, and updated as changes are made in either tool.
Report on requirement status
Custom fields can be visualized and reported on using the powerful Aha! reporting capabilities. As engineers make status updates or changes, those changes are reflected back in Aha! With all that data at your fingertips, it is easy to create beautiful reports and visualize status to see how work is progressing. For example, the List report below shows the status of each Requirement with its component, status, and even a link to the associated JIRA issue. Custom fields added to Requirements can be analyzed using the reporting capabilities in Aha!
Easily map requirement custom fields with JIRA
To take advantage of this update to the integration, you will need to create custom fields in both Aha! and JIRA. Adding custom fields in Aha! requires both Customizations Administrator and Product Owner permissions. After selecting the corresponding issue type that Requirements will map to, you can select from wide range of custom fields including Text fields, Number fields, Date fields, Pre-defined choice fields, Editable choice lists, Pre-defined tag fields, Tag fields, and Note fields.Define which fields should be mapped between Aha! and JIRA.
While you were reading this, at least a few more requirements were created. And with this update to our JIRA integration, engineering will soon make them a reality.
Every week it feels like we hit a new milestone, thanks to your passionate ideas — so keep telling us what you need. Because while big numbers are fun, your happy use of Aha! is what really keeps us motivated.
Sign up for a free Aha! trial — be happy
The Aha! and JIRA integration and this new capability 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 of Aha! now to see why over 50,000 users trust Aha! to set product strategy, create visual roadmaps, and prioritize releases and features.
All product and company names herein are trademarks of their respective owners.