Skip to Main Content
ADD A NEW IDEA

FILTER BY CATEGORY

Jira

Showing 206

Fix field population in Aha/Jira integrations to only rely on email address or other specific data

Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
Guest 14 days ago in Jira 0

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 22 days ago in Jira 0 Future consideration

When sending an Epic to Jira, allow sending of all /updates to Features

Currently, when you send an Epic to Jira, all of its features are sent, but they are sent as the default Feature type instead of the types that they were actually categorized. Often the product person is working in Aha! and doesn't want to yet sen...
Karie Kelly about 1 month ago in Jira 0 Future consideration

Ability to use "belongs to" relationship in Aha to map to "is contained by" link type in Jira

I don't see a way to connect Aha's "native" record hierarchy to a similar hierarchy in Jira. Using epic --> feature as an example, if I select the parent epic while editing a feature, that creates a "Belongs to epic" relationship under that fea...
Gene Lewin about 1 month ago in Jira 1 Already exists

Urgent Jira Integration Needs: Resolution, Resolved Date & Percent complete

These are critical to the success of our organization wide integration efforts which are ramping up very soon. Set a resolution in Jira when record is closed in Aha When Jira issues are closed the user is required to set a resolution during the tr...
Marcie Gardner about 2 months ago in Jira 2 Future consideration

Allow integrations such as Jira at the Product Line level

Integrations may be common across products within the same product line. It would save time and the possibility to make setup mistakes if these integrations can be setup one level higher
Guest about 2 months ago in Jira 0 Future consideration

Make JIRA webhooks URL specific

Currently JIRA webhooks function globally which means we cannot have separate webhooks with filters from multiple Aha workspaces to one shared JIRA project. In this use case there is a large offshore team that is shared by several products within ...
Guest about 2 months ago in Jira 0 Future consideration

Automatically create/update Notification Groups based on location hierarchy

I have a JIRA 2.0 integration setup for one of my workspaces. When I push over an Epic containing Features and Requirements, the Features are linked to the Epic but the Requirements are not linked to the Feature. So in JIRA, you can easily see how...
Guest 2 months ago in Jira 0 Future consideration

The Aha <->Jira Integration Mappings should be Transparent to User

Presently, the record level mappings between Aha and Jira are opaque to the user. This makes it quite difficult for the user to debug the syncing.Without this info, it is quite challenging to get the Integration working. If the integration does no...
Guest 3 months ago in Jira 1 Already exists

Enable external link handling for Jira and other integrations

Jira has a native link handling functionality that displays links in-line on issues. To recreate the same behavior, I have to create a custom field for the link to target (meaning I end up with a bunch of extra fields) and need to reciprocate acro...
Yancey Larochelle-Williams 4 months ago in Jira 0 Future consideration