Jira
Sort by:
Recent
Status:
Future consideration
Showing 175
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
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
6
VOTE
Integrate Master Features and related features to different JIRA projects
In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...
1
Future consideration
7
VOTE
Allow child integrations to inherit the "run-as" user from an integration template
The following idea is for the JIRA integration, but could describe integrations to other development tools using a similar web hook mechanism.
The integration template functionality allows settings from a master template to be adopted by child int...
0
Future consideration
1
VOTE
Have features push a status to a field in Jira when deleted
As a product manager I would like the ability to keep track of which items in JIRA/AHA have been deleted in each system. I know Aha! will not likely implement a feature to delete issues in Jira when respective items are deleted in Aha! However it ...
0
Future consideration
18
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
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
4
VOTE
Teach aha custom fields to auto-update its list of values based on JIRA custom fields
Dear aha, we have custom fields in JIRA, that we would like to keep in sync with mapped custom fields in AHA. Good example is a list "Country". We have that as global jira custom field with specific value list enabled per jira project. Whenever a ...
0
Future consideration
8
VOTE
"Make everything OK" button on feature that triggers insert/update/delete/move JIRA->AHA
Hello, it would be very helpful if in scenario, where aha records are linked to dev tool records (e.g. JIRA), there would be a possibility to trigger full record update for a single record. Example: integrations config: Features linked to Epics in...
10
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved