Jira
Sort by:
Popular
Status:
Likely to implement
Showing 265
2
VOTE
Ability to import child records when connecting to an existing record in Jira
What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
0
Future consideration
2
VOTE
Defect: Jira Integration record mapping doesn't use custom terminology
Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
0
Future consideration
2
VOTE
Automatically update roll-up release name in integrations
Who would benefit? Teams using roll-up releases extensively. What impact would it make? Easily keeping everyone informed of launch details. How should it work? When the user updates the name of the roll-up release, it should be updated in any mapp...
0
Future consideration
2
VOTE
Add more filters to integrations import
Who would benefit? aha admins What impact would it make? keeping Aha in sync with JIRA on the release. This would also help other internal stakeholders informed. How should it work? The integrations import desperately needs additional filtering cr...
0
Already exists
2
VOTE
Support of Embedding of Ideas in Confluence
As a user, I want to embed ideas within Confluence so the idea status is automatically updated as the feature is being developed. My use case is as follows: A customer I am working with ran into a weird edge case. I document the workaround in Conf...
0
Future consideration
2
VOTE
Copy integration mappings for records at the same hierarchy level
When configuring an integration between Aha! and a development tool, you decide what records in Aha! map to what records in the development tool and map the individual fields. It's common to have multiple record types in a development system at th...
0
Future consideration
2
VOTE
JIRA Integration - Allow Changing Board
We recently had to migrate JIRA tenant to another existing one (as the result of an acquisition). Whilst I was able to just change the server address and the integration URLs pointed to the correct location of the migrated issues, the board used f...
0
Future consideration
2
VOTE
Allow Mapping of Requirement Type from Jira to Aha!
Presently, you can map types for items at the Feature level and this syncs between Jira and Aha! without issue if the item type changes in Jira; However, the issue that we are facing is that because there's no mapping between Jira and Aha! for req...
1
Future consideration
2
VOTE
Ability to use "belongs to" relationship in Aha to map to "is contained by" link type in Jira
I don't see a way to connect Aha's "native" record hierarchy to a similar hierarchy in Jira. Using epic --> feature as an example, if I select the parent epic while editing a feature, that creates a "Belongs to epic" relationship under that fea...
1
Already exists
2
VOTE
Make JIRA webhooks URL specific
Currently JIRA webhooks function globally which means we cannot have separate webhooks with filters from multiple Aha workspaces to one shared JIRA project. In this use case there is a large offshore team that is shared by several products within ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved