Jira
Sort by:
Recent
Status:
Future consideration
Showing 170
1
VOTE
Ability to Integrate Ideas with Jira Service Desk
What is the challenge? I am using a Jira Service Desk to capture new product and project requests and would like to use the Aha! Ideas for review and prioritization before sending to a specific Aha! Product Workspace. What is the impact? Today I h...
0
Future consideration
5
VOTE
Epic progress doesn't update when it has children in different projects
Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
0
Future consideration
1
VOTE
Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
0
Future consideration
2
VOTE
Automatically update roll-up release name in integrations
Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...
0
Future consideration
3
VOTE
Excel Documents Not Sending to Jira Custom fields
Who would benefit? What impact would it make? Less back and forth with BA and Developers to correct transfer error How should it work? Underneath our field "Functional Requirements" in the attch items, when I attach an excel document it does not t...
0
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
Jira Integrations: Map Aha Releases to a custom Jira Version Field
Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...
0
Future consideration
5
VOTE
Improving handling when Jira users change issue type across record hierarchy
Who would benefit? Users of Jira integration What impact would it make? Users who are changing issue types in Jira after records are integrated. How should it work? Right now, if a Jira user changes an issue type on an integrated record, the integ...
0
Future consideration
3
VOTE
Allow editing to wiki-rendered fields in Jira
Who would benefit? Jira integration users What impact would it make? Currently Jira is sending broken formatting when fields leverage wiki-rendering with tables How should it work? If a user makes an edit to a table in Jira on a wiki-rendered fiel...
1
Future consideration
1
VOTE
Allow one-way mapping of calculated/read only Jira fields into Aha
Who would benefit? Aha users needing to see Jira data that is not editable in Jira What impact would it make? In our case, allow us to use engineering estimation data in Aha scorecard calculations. How should it work? The current Aha-Jira integrat...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved