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...
Integrations 2.0: Support importing unmapped issue types
In 1.0 you could map Features to Stories but also set the JIRA integration to support importing unmapped types.
This meant that bugs, tasks, etc created in JIRA could be imported as Features in Aha!
This is important, without this we have no way t...
Jira tickets support embedded images using the following format.
Jira Image Formatting Notation
We make very heavy use of this feature to pull our designs into the jira tickets...
Allow a Feature (epic) in Aha! to have Requirements (stories) that live in a different Jira project
The use case is that we create features in Aha! and sync them to Jira as epics. The development team will then break the epics down further into stories in the appropriate Jira projects for the teams that need to work on them. In Jira, these stori...
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...
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...
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...
Improved automatic pull of items from Jira to ensure strategic relevance of Aha!
As a product manager with an engineering team that uses Jira, I understand and appreciate that Aha aims to remove the temptation for anyone to "sneak" tasks into Jira rather than through the PM and Aha!. The reality, though, is that agile sprints ...
Turn off 2-way synch for specific custom fields sent to Jira
Up until recently, custom field data was sent one-way Aha to Jira.
For certain fields, we prefer the data sent one-way. We want to be able to send information such as business goals so that people using Jira can understand more about what's tryin...
almost 8 years ago
Guide users to reload configuration when missing field in mappings
When new fields are added in the development system, they are not automatically shown in the Aha! integration mappings screen. Users do not intuitively know to click the "Reload configuration" button, and also do not know to check the Jira create/...
about 1 year ago