Jira
Sort by:
Trending
Status:
Showing 272
3
VOTE
Support mapping Asset object fields through Jira integration
Who would benefit? Customers using the Asset object through Jira Service Management. What impact would it make? When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira int...
0
Future consideration
18
VOTE
Convert story to epic in Jira when promoting requirement to feature
In Aha! I have a feature with a set of requirements, all of which has been pushed to Jira as an epic with a set of stories. I want to convert one of the requirements to a new feature in Aha! and have the corresponding story in Jira changed to an e...
2
Unlikely to implement
2
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
10
VOTE
Custom scorecard components/elements are available for reports but NOT for integrations.
We actually would like to display the individual pieces that comes our WSJF scorecard for our initiatives in Aha. Right now, I can pull the individual scores into an Aha report, but I'm not able to send the same data to JIRA. We use dashboards in ...
3
Future consideration
3
VOTE
Allow editing to wiki-rendered fields in Jira
Who would benefit? Jira integration users What impact would it make? Currently Jira is sending broken formatting when fields leverage wiki-rendering with tables How should it work? If a user makes an edit to a table in Jira on a wiki-rendered fiel...
1
Future consideration
10
VOTE
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
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
2
VOTE
Ability to import child records when connecting to an existing record in Jira
What is the challenge? We often have the use case where we need to connect an Aha! epic to an existing Jira record, and that Jira record will also likely have child tasks/stories. The existing connection logic will only sync with the epic record, ...
0
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
© 2025 Aha! Labs Inc.•All rights reserved