Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
When creating Epics in Jira, they don't integrate into Aha. They will only integrate if you create child records under them that integrate into Aha. Epics need to be able to be integrated into Aha on their own.
Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item.
Example: Support reports a "Support Defect", Dev reviews, changes i...
over 4 years ago
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status
When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow.
It would be great to also access the Resolution status from Jira to handle this c...
about 7 years ago
Improve warning for integrations "Update Records" action
For a development tool integration (i.e. Jira), there's an "Update Records" button. When clicked, you get this attached warning. This doesn't warn you that Aha! will send data for any one-way mapped fields (Aha! --> Jira) as well. It would be h...
about 1 month ago
Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature
The specific use case that this commonly occurs for is the following mapping:
Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well.
Current behavior: The i...
over 6 years ago
It would be helpful if we could use the Jira integration to send features to a specific board. We have several dev teams working within a single project, but they utilize different broads. We would like to send a feature to open a record is a spec...
5 months ago
When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Jir...
almost 7 years ago
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...