Jira
Sort by:
Trending
Status:
Showing 260
1
VOTE
Automatically push Epics/Features in Aha! to JIRA
What is the challenge? As a product manager using Aha!, I want to be able to create an Epic or Feature and have it automatically push to JIRA (even it's a shell that is not definition complete), so that it is represented on the JIRA board where I ...
0
Future consideration
1
VOTE
Flag a broken JIRA integration to the Aha! admin so it can be resolved
What is the challenge? As an Aha! admin, I want to ensure the JIRA to Aha! integration flags errors to me proactively (via email would be great), so that errors in the integration setup can be immediately addressed. What is the impact? As an Aha! ...
0
Future consideration
15
VOTE
Support for Jira Code Markup
Need to support the Jira code markup option.
If the developer enters sample code as part of the description in Jira, the description gets updated in Aha!
However the code markup is translated into very large tables in Aha!
At some point, Aha! upda...
2
Future consideration
9
VOTE
Allow requirements to be associated with the release record
The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...
0
Future consideration
8
VOTE
Please Add a Setting to Turn Off the Automatic Imports of Unlinked Jira User Stories
I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!.
We'd much prefer that this not be the ca...
1
Future consideration
14
VOTE
When an Idea is Promoted to a Feature, Automatically Copy Idea's *Subscribers* (as well as Watchers) to the Feature. And, Sync the Watchers & Subscribers to JIRA
Hi All,
We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very he...
4
Unlikely to implement
13
VOTE
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
9
VOTE
The Jira integration should allow the sending of a release to Jira and properly map the feature types to Jira issue types.
Today, sending a release converts all the feature types to the default Jira issue type specified in the Jira integration mappings. This makes the release level integration useless if you manage different feature types in Aha (e.g. bug, defect, fea...
1
Future consideration
11
VOTE
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field
Expose "Estimate" at story creation in AHA! and push to JIRA "story points" field - prevents having to go to JIRA and add points individual after time spent planning in AHA! - efficiency for PMs and Engineering
1
Already exists
© 2025 Aha! Labs Inc.•All rights reserved