Jira
Sort by:
Recent
Status:
Future consideration
Showing 174
1
VOTE
Change Button Click to Dropdown for Integration Screen
When completing the Integration, a user is asked to click through the various buttons showing the direction of the integration. A user has to make several button clicks to change the option, which is not always convenient. A drop down menu would b...
0
Future consideration
6
VOTE
Better display of user info from Jira integration
When comments are added to Aha from the Jira integration, they show up as having been created by Integration: Jira even though the comment includes the following:
Created in Jira by Matthew Monahan (****@****.com)
When I dig into the values in t...
0
Future consideration
6
VOTE
Set Rank order from Jira to Aha!
When configuring a new Product in Aha to integrate with Jira: The backlogs are already in priority order in Jira. However, when syncing over to Aha!, the priority order does not carry over upon the first sync. I understand how to use the rank fiel...
1
Future consideration
1
VOTE
Features assuming the same release as its parent master feature when importing from Jira
Given that I have an epic in Jira, linked to a Master Feature in Aha
And the Master Feature is found in "Release X",
When I create a story beneath that epic in Jira,
Then the story should be imported as a child to the Master Feature,
AND assume ...
0
Future consideration
1
VOTE
Working with JIRA worklog dimension (worklog date)
Dear aha, in order to resolve reporting of time spent on features within specific timeframes, it might be useful to think about including worklog date of JIRA issues into synchronized aha backlogs. This would enable creation of reports where not o...
0
Future consideration
1
VOTE
Allow Feature or Master Feature to be pushed to Jira when the Aha! state is mapped but blocked when it is un-mapped
Our product management team wants to plan features prior to making the feature available via Jira Integration. For example while a feature is under consideration or in planning/grooming state it would only exists in Aha. Once the feature is ready ...
0
Future consideration
5
VOTE
3
VOTE
JIRA integration Import of only linked epics
When stories in JIRA are moved between epics they are not automatically updated in aha. Also, for stories created prior to mapping a JIRA epic the stories are not automatically imported to aha. The import can be used to pull these in but the Impor...
0
Future consideration
4
VOTE
Integration with JIRA needs better Error handling support
Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
1
Future consideration
5
VOTE
We need the Initiative ID available in JIRA integrations so they can be reference-able in other tool dashboards.
We use the Aha API to populate views in Tableau. The Initiative [API] ID is a crucial portion of making sure what we sync to JIRA from Aha and what we are looking at in Tableau which provides a combined view of both tools, is one and the same. I a...
1
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved