Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 171

Update API integrations with JIRA to add Created Date and Resolved Date

We would like to be able to map the created date as well as the resolved date to fields within aha from JIRA.
Guest over 3 years ago in API / Jira 1 Future consideration

Ability to create a report of integration errors across multiple workspaces

Currently the only way to look at the integration errors across multiple workspaces is to bring up the Integration Updates dialog and use the Send outgoing changes tab. But you can't filter on error text, or expand the window to see the everything...
Jor Bratko over 3 years ago in Jira 5 Future consideration

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...
Stephanie Lechner about 1 year ago in Jira 0 Future consideration

Populate Jira Components via Integration

Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
Guest almost 2 years ago in Jira 0 Future consideration

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, ...
Nerissa Muijs 9 months ago in Jira 0 Future consideration

JIRA integration needed at the portfolio and product family levels.

We use initiatives at all levels within Aha and need to be able to integrate those with JIRA for additional capacity reporting. If initiatives are available to be entered on those levels, it would be useful to have the integration setup available ...
Wen-Wen Lin over 5 years ago in Jira 2 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 over 2 years ago in Jira 1 Future consideration

Jira integrations : Add the capability to use filters instead of boards to set up integrations

What is the challenge? the boards only have tickets currently worked on , we want to load all tickets , so we can plan , this is because the team sometimes their create their own What is the impact? if you need to split a jira project with multipl...
Guest 5 months ago in Jira 0 Future consideration

Filter noise from Jira integration logs

The log file currently reports on Jira tickets that are out of scope for the integration (e.g., bugs, stories, tasks) as defined by the integration template. These log entries typically end with "No changes made in Aha!" If I'm trying to find the ...
Sandy Kobayashi almost 2 years ago in Jira 0 Future consideration

Ability to see more than the last 200 logs in Aha-Jira Integrations

Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...
Guest almost 5 years ago in Jira 2 Future consideration