JIRA Import multiple issue types as requirements mapped to parent feature
As a PO, I’d like to import multiple issue types (i.e. bug, story) as requirements that map to their parent features so that existing Jira Projects can be imported into Aha! Products in a single import
Need to "Link with existing issue in JIRA" at requirement level
We have JIRA and Aha today and the tools are integrated as follows:
Aha feature - JIRA Epic
Aha requirement - JIRA story
NA - JIRA sub-task
For some reasons, I had to delete the integration with JIRA for a specific product line from Aha an...
Would like to be able to view the sprint a feature is currently assigned to in JIRA. It looks like we have most of the other fields available for mapping but that one isn't available. I get a ton of questions about when a feature is scheduled to b...
Support referencing JIRA ID / JIRA Key attribute in calculated columns
What is the challenge The JIRA ID and JIRA Key are reportable attributes within Aha! and they were recently updated so they could be filtered in the reports. However, I need to reference these fields for custom calculations. What is the impact? I ...
If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.
Support for an Aha! Initiative to create/map to Epics across multiple JIRA Projects
The use case is a requirement to have a single Aha! Initiative create/map to Epics that are in different JIRA Projects. Current support is that an Aha! Initiative can only be linked to a single JIRA Epic. Simple example: Fredwin Cycling has an Epi...
Ability to "lock" a custom field, so no user can edit it
Some of our fields in Aha are solely dictated by the field in Jira, for example Status.
Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrite...
Provide ability to map Created by user to Reporter field in the JIRA integration
When sending or linking a Aha feature to a Jira Epic the system uses the name of the person who created the Jira integration record instead of the user who created the epic. This results that all Jira issues now show up as Reported By with the nam...
It's helpful for the scrum teams to not only see the Aha rank but also the business value associated with the scorecard. Integrating scorecard with JIRA Business Value is beneficial to members of the teams as well as reporting on the business valu...