Jira
Sort by:
Trending
Status:
Future consideration
Showing 261
4
VOTE
JIRA Integration - allow bidirectional mapping of the "time frame" field
for those who map epics to initiatives, and like to keep their platforms bidirectionally synced as much as possible, it's possible to have a custom "time frame" field in JIRA set up to match that in Aha, yet it's not possible at the moment to bidi...
1
Future consideration
1
VOTE
Inform user if Version export to Jira fails due to existing fix version in Jira
Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
0
Future consideration
5
VOTE
Allow "Predefined choice list" to select multiple items
Jira has the ability to have a custom field with selecting multiple items in a list. Aha can only support single items. The Aha multiple tags functionality is incompatible with Jira selects. We would like the ability to specify 2 or more items in ...
0
Unlikely to implement
4
VOTE
Link user stories (requirements) in JIRA when under the same epic (feature)
We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
2
Future consideration
2
VOTE
Ability to map Jira Web Links with Aha! URL at Integration
Why is it useful? Web links at Jira are used to show all the links associated to an issue/record. Who would benefits from it? Its easy for all users to view Aha! link at Jira epic or story rather than having it at a custom field. How should it wor...
0
Future consideration
2
VOTE
JIRA integration to track correct users in history of issues
Today the Aha JIRA integration will leverage the user account setup in the integration settings as the actor for all integration sends between the systems. This creates a lot of confusion for who actually made changes in one system or the other. F...
1
Future consideration
3
VOTE
JIRA integration Import of only linked epics
When stories in JIRA are moved between epics they are not automatically updated in aha. Also, for stories created prior to mapping a JIRA epic the stories are not automatically imported to aha. The import can be used to pull these in but the Impor...
0
Future consideration
4
VOTE
History of items created via integration
In Jira integration 2.0, there's no link or reference to the items created by the integration once you approve them.
A modal notification like you currently use would work at a one-by-one level. If that makes sense.
Even better would be a tab in ...
1
Future consideration
1
VOTE
Allow Mapping of Requirement Type from Jira to Aha!
Presently, you can map types for items at the Feature level and this syncs between Jira and Aha! without issue if the item type changes in Jira; However, the issue that we are facing is that because there's no mapping between Jira and Aha! for req...
0
Future consideration
3
VOTE
Ability to aggreate work done value from both feature and requirements
Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when:
1. there is a time log in JIRA on epic (synced to feature)
2. there is a time log...
2
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved