Jira
Sort by:
Trending
Status:
Showing 269
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
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
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
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
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
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
9
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...
1
Future consideration
4
VOTE
Child records eligible to import to multiple workspaces are automatically importing to the workspace where the parent record is integrated to
What is the challenge? If I am using an integration template to manage multiple Jira projects which can have parent/child records spanning multiple Aha! Workspaces (many to many relationship), If I add a child record from one Jira project to an in...
0
Likely to implement
1
VOTE
Ability to import JIRA labels to Aha Requirement Tags
What is the challenge? Unable to import JIRA labels to Aha Requirement Tags What is the impact? DSG tracks in JIRA Stories which business silo owns the work with Tags and tags if the work is carry over from a previous springs. DSG needs those tags...
0
Future consideration
2
VOTE
Moving integrated Jira records to a new project should update the Jira link and key in Aha!
What is the challenge? When following the guidance in this help article to move Jira records between Jira projects with Jira, https://support.aha.io/aha-roadmaps/integrations/integration-guides/move-records-with-jira-or-rally~7444656710918981281#p...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved