Jira
Sort by:
Recent
Status:
Future consideration
Showing 170
1
VOTE
Add option to show additional columns/fields in "Integration updates" window for Jira
The "Integration updates" window currently only shows the issue summary of incoming issues. Presumably the JSON payload being received by Aha contains the full set of information for the incoming issue ... it would be incredibly valuable to be abl...
0
Future consideration
3
VOTE
Add better error handling for 'unhandled error exceptions'
When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
0
Future consideration
1
VOTE
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
3
VOTE
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
6
VOTE
Allow for parent-child linking across Jira projects without using an integration template
Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
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
1
VOTE
1
VOTE
Inform user if Version export to Jira fails due to existing fix version in Jira
Problem If a Version is exported from Aha to Jira using the integration, and a fix version with that same name already exists in Jira, Jira will response with HTTP status code 400, and a JSON payload: {"errorMessages":[],"errors":{"name":"A versio...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved