Jira
Sort by:
Status:
Showing 267
37
VOTE
Integrations 2.0: Add dependency link to connect records without natural relationships together
In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...
3
Future consideration
1
VOTE
Add "Idea votes" and "Account" to the list of idea fields that can be mapped to Jira
What is the challenge? We cannot see information on the account that an idea came from or how many votes an idea has in Jira What is the impact? Product Manager's time is wasted going back and forth to remember where an idea came from or to pass t...
0
Future consideration
20
VOTE
12
VOTE
Provide alternative way to match users when email address is not exposed in Jira
Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
1
Future consideration
2
VOTE
Map custom release field in Jira integration
Currently the Jira integration doesn't allow users to map the custom release field, on records like features. We would like to be able to map this field and ideally to map it with a custom versions field in Jira. The two fields should be able to m...
0
Future consideration
6
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
14
VOTE
Ability to create a report of integration errors across multiple workspaces
Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
6
Likely to implement
2
VOTE
Allow automatic imports of child records when parent records exist in a different workspace
What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
0
Future consideration
22
VOTE
Update JIRA integration when feature ranking changes in Aha
I have a Aha to JIRA integration set up which allows me to prioritise features in Aha by a combination of Rank and Score. We frequently re-prioritise cards in Aha (therefore changing the rank) but this doesn't trigger an update in JIRA. I rarely c...
6
Unlikely to implement
6
VOTE
Allow for parent-child linking across Jira projects without using an integration template
Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved