Skip to Main Content
ADD A NEW IDEA

Jira

Showing 257

Improve integration job troubleshooting steps

To help me quickly troubleshoot background job logs: Tag each Update all linked records job type with the integration name. You are already doing this with Integration Import job types. In the case where a background job has failed, you write in t...
Alfred S about 2 years ago in Jira 0 Future consideration

Hover text on Jira integration to show project & board

In workspace settings, once an integration is established, it would be nice to be able hover over the integration and see at a glance the project and board without clicking into the integration and looking at the project/board setup.
Guest about 2 years ago in Jira 0 Future consideration

New "integration reference" custom field type to house read-only text reference to a field on other side of Jira (or other) integration

There are fields in Jira (and I imagine other integrated applications) that don't map cleanly to an Aha custom field type. I am proposing a new custom field type that is an always-readonly text field that can be mapped to any Jira field type, and ...
Gene Lewin about 2 years ago in Jira 0 Future consideration

bi-directional epic status mapping with Jira

I want to be able to map 1-way a specific status change between Aha and Jira
Guest about 2 years ago in Jira 3 Future consideration

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 about 2 years ago in Jira 1 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 over 2 years 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 over 2 years 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 over 2 years 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 over 2 years 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
Steve C over 2 years ago in Jira 5 Planning to implement