Jira
Sort by:
Trending
Status:
Showing 268
1
VOTE
Need configuration to allow allow/block execution system (JIRA) initiated Epics back to Aha
For Epics which get initiated in Aha and flow down to JIRA, we want to enable 2-way integration so that updates which happen in JIRA are realized in Aha. However, if a NEW Epic is initiated on the JIRA side, we may not want that to be visible in A...
1
Already exists
1
VOTE
Automatically reduce feature estimate when requirement is completed
When using the requirements level estimates to drive the total estimate on the feature level we would like the feature level estimate to be reduced when a requirement is marked in a complete status. Also we would like to have the feature status au...
0
Already exists
1
VOTE
"Update JIRA" option for Requirements
If I update a Requirement after the Feature has been synced to JIRA, I want to be able to immediately have the corresponding Story in JIRA updated to match it. The synchronisation seems to take more than 10 minutes to go through.
Like we have Acti...
0
Already exists
1
VOTE
Fix Time Tracking Totals when using Requirements
Currently: With the JIRA 1.0 integration. When using Requirements for Time Tracking the "Total Time" is not displaying the correct data.
In Aha the Time Tracking says 73d 4h.
Screenshot "Aha Time Tracking.png"
In Jira the Time Tracking says 2w ...
1
Already exists
1
VOTE
Integrations 2.0 - Only show valid integration directions for Release <-> Fix Version
Integrations 2.0 - Please only show valid integration directions for Release <-> Fix Version.
I had opened ticket https://support.aha.io/hc/requests/176083 because I could not connect to the Jira version using Actions > "Link with existin...
0
Unlikely to implement
1
VOTE
1
VOTE
Prevent "roadmap drift" by displaying JIRA Epic labels next to Aha! Requirements.
This idea is a proposed work-around to this problem: https://big.ideas.aha.io/ideas/APP-I-2702. Until that problem is fixed, I need an easy way to spot when Requirements and Stories have inadvertently drifted (i.e. Stories have been moved to anoth...
0
Will not implement
1
VOTE
Update JIRA with updated Aha Requirement definitions
When we update a requirement in Aha with a new or updated requirement definition, and there is already an existing JIRA link, the updated copy doesn't transfer over to the JIRA User Story, even when we select "Update JIRA" from the Actions menu.
1
Already exists
1
VOTE
Two-factor authentication for the integration Aha! to JIRA
Quoting my mail replying back to Brian deHaaff:
Hi Brian,thanks a lot for the offer to help with my onboarding – the idea to trigger this communication from the Founder / CEO indeed transports a feeling of importance that makes it hard not to resp...
0
Unlikely to implement
1
VOTE
Provide the ability to map multiple ticket types to requirements
We are hooking Features into Epics, and discussing with development and the rest of the product team, the individual enhancements, new features, and tasks that are required to be performed for the "Epic" to be completed. Aha/Jira integration only ...
3
Already exists
© 2025 Aha! Labs Inc.•All rights reserved