Jira
Sort by:
Trending
Status:
Showing 265
7
VOTE
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
0
Planning to implement
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
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
1
VOTE
Allow to manually push a Jira Theme to Aha as an MF ( without the need of a ready MF on Aha side)
What is the challenge? Currently we have cases where RnD would open a theme (we categorize it) , and that is for mostly themes with technical nature. as such PM will not initiate them, but we still want the PM to be aware of them in planning and p...
0
Future consideration
2
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
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
1
VOTE
Send over images as correct size when integrating from Aha to Jira
What is the challenge? Steps: Create a feature in Aha and add a screenshot within the description. Send the feature to Jira. Result: In Jira, the image has a bunch of white space to the left and right of the image. So the image is small in Jira. W...
0
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
47
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
© 2025 Aha! Labs Inc.•All rights reserved