Jira
Sort by:
Trending
Filter by:
Status
Showing 272 of 9657
5
VOTE
Allow "Predefined choice list" to select multiple items
Jira has the ability to have a custom field with selecting multiple items in a list. Aha can only support single items. The Aha multiple tags functionality is incompatible with Jira selects. We would like the ability to specify 2 or more items in ...
0
Unlikely to implement
3
VOTE
Make fixed workflow transition enforcement optional for Jira integratations
Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it.
With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need A...
0
Future consideration
3
VOTE
Ability to enforce mandatory fields on Starter Roadmap, User Story Map, Strategy Roadmap, and Gannt
We have mandatory fields when creating initiatives, master features and features. These can be avoided when creating records via the Starter Roadmap, User Story Map, Strategy roadmap and Gantt views (there are probably some others I'm missing here...
0
Future consideration
4
VOTE
Link user stories (requirements) in JIRA when under the same epic (feature)
We have features in Aha mapped to epics in JIRA, and then requirements mapped to user stories. I'd like the user stories in JIRA that I send over to automatically include links to their sister stories under the same epic, so that developers can ea...
2
Future consideration
1
VOTE
Allow one-way mapping of calculated/read only Jira fields into Aha
Who would benefit? Aha users needing to see Jira data that is not editable in Jira What impact would it make? In our case, allow us to use engineering estimation data in Aha scorecard calculations. How should it work? The current Aha-Jira integrat...
0
Future consideration
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
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
4
VOTE
Only update Jira FixVersion if the Release has actually changed in Aha and the Jira FixVersion has not been edited
In my process I want Aha to be my master in terms of planning, but allow Jira to update details as actual releases are made. By this I mean that I will plan a release such as "Q4 2017" in Aha and push to Jira. As work is completed in Jira the issu...
0
Unlikely to implement
1
VOTE
3
VOTE
Ability to aggreate work done value from both feature and requirements
Dear aha, in our scenario when AHA is synced with JIRA with time tracking attributes, we come into a problem with showing the complete work done on the feature when:
1. there is a time log in JIRA on epic (synced to feature)
2. there is a time log...
2
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved