Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

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...
Mike Wachal over 2 years ago in Jira Future consideration

Integration with JIRA needs better Error handling support

Aha! integration with JIRA does not notify users on errors that would have happened during the integration (i.e. push/pull). This keeps the users in dark on what would have gone wrong and requires manual intervention to detect errors.
Guest over 6 years ago in Jira Future consideration

Need easier way to link to existing Jira records!

Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...
Jon DeLong almost 4 years ago in Jira Future consideration

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...
Wen-Wen Lin over 6 years ago in Jira Future consideration

Capability to tag JIRA users

As a user with an integration with JIRA, I want the ability to @ users in my feature, requirement, or comments in Aha and the @ will sync to the JIRA users available so they can receive a JIRA notification. Our dev team does not use Aha notificati...
Guest almost 8 years ago in Comments / Notifications / Jira Future consideration

JIRA Integration - Hide 'Send To' Options

Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Kyle Kinder over 2 years ago in Jira Future consideration

Support of Embedding of Ideas in Confluence

As a user, I want to embed ideas within Confluence so the idea status is automatically updated as the feature is being developed. My use case is as follows: A customer I am working with ran into a weird edge case. I document the workaround in Conf...
Amelia Peklar over 2 years ago in Jira Future consideration

Ability to configure integrations not to create new records in Aha

In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA. I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...
Kevin Burges about 8 years ago in Jira Future consideration

Copy integration mappings for records at the same hierarchy level

When configuring an integration between Aha! and a development tool, you decide what records in Aha! map to what records in the development tool and map the individual fields. It's common to have multiple record types in a development system at th...
Emily Yankush over 2 years ago in Jira Future consideration

Enable Field Filters for when to Sync to Aha

I would like to be able to set a filter in my Integration for which Jira Issues to sync up. An example would be to not push stories into Aha until there is a point value or time estimate entered in Jira. Another would be to only push to Jira if it...
Kenny Burnham almost 7 years ago in Jira Future consideration