Jira
Sort by:
Trending
Status:
Unlikely to implement
Showing 263
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
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
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
5
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
5
VOTE
Record successful updates in Aha! from Jira "update records" action
What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...
0
Future consideration
46
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
70
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
5
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
4
VOTE
Allow Jira Team Custom Field to Integrate with Aha! Predefined Choice Fields
What is the challenge? The Jira Team field in Jira can only be mapped to string-based fields like notes and text fields. There is no way to configure this field with predefined choices that match the available teams in Jira. What is the impact? Us...
0
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
© 2025 Aha! Labs Inc.•All rights reserved