Jira
Sort by:
Trending
Status:
Unlikely to implement
Showing 270
57
VOTE
Jira Integration of custom calculated field
We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...
3
Future consideration
9
VOTE
Synchronize Aha! organizations custom field with Jira Integration
What is the challenge? We heavily use the Organizations custom field in Aha to map customer engagement and roadmap transparency and need that info to sync to our Jira instance. What is the impact? Disconnected systems, duplicate data entry, poor u...
2
Future consideration
1
VOTE
Add an option for JIRA integration to re-import all stories under an epic
What is the challenge?
Sometimes we links epics after they are created. In this case stories aren't linked automatically. That means we need to do an extra step to import the stories
What is the impact?
Error prone and aha doesn't reflect ...
0
Future consideration
18
VOTE
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
2
Future consideration
11
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...
2
Future consideration
49
VOTE
Complete Auto Import Functionality -- not just children of existing linked records
This is regarding the JIRA integration feature:
Automatically Import New Records:
Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
5
Future consideration
2
VOTE
Jira & Aha Integration - Ability to refresh Aha records making either Jira or Aha the dominant source
What is the challenge? We would like to have the ability to refresh the Aha record based on Jira updates. Currently, inside the integrated Aha ticket, users can only resend the updates they made in Aha into Jira, but not the other way around. We w...
0
Future consideration
71
VOTE
Handle multiple FixVersions in JIRA
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
17
Future consideration
6
VOTE
Sync comments between Jira & Aha!
What is the challenge? Unable to Sync deleted and edited comments between Jira and Aha! What is the impact? Syncing deleted and edited comments between Jira and Aha! is crucial to maintaining accurate and up-to-date communication across teams. If ...
1
Future consideration
3
VOTE
Temporarily disable notifications - “update record” button
What is the challenge? We have a Jira-Aha integration template that span across multiple Aha workspaces. When we change the integration template (add/remove fields for instance) we need to sync data between Jira and Aha to ensure both systems are ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved