Jira
Sort by:
Trending
Status:
Showing 264
5
VOTE
Populate Jira Components via Integration
Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
0
Future consideration
25
VOTE
Allow To-Do's to be mapped to JIRA Issue Types
We would like to be able to make better use of Aha To-Do's so that they carry over to our JIRA Agile installation. Currently we have Initiatives mapped to Epics, Features Mapped to Stories and Requirements Mapped to a custom JIRA type of Requireme...
5
Unlikely to implement
7
VOTE
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...
1
Future consideration
3
VOTE
Support mapping Asset object fields through Jira integration
Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
0
Future consideration
1
VOTE
Ability to sync Jira's "Team" bidirectionally
What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
0
Planning to implement
5
VOTE
5
VOTE
Filter noise from Jira integration logs
The log file currently reports on Jira tickets that are out of scope for the integration (e.g., bugs, stories, tasks) as defined by the integration template. These log entries typically end with "No changes made in Aha!" If I'm trying to find the ...
0
Future consideration
1
VOTE
Ability to update Jira Affects Versions field from Aha via integration
What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...
0
Future consideration
1
VOTE
Map detailed estimates by initiative in Jira integration
What is the challenge? Right now, you cannot map detailed estimates by initiative. You can only map estimates for Epics, Features, and Requirements. What is the impact? When trying to estimate at a higher level and leveraging initiatives, you cann...
0
Future consideration
2
VOTE
Ability to import child records when connecting to an existing record in Jira
What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved