Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Showing 264

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

Sync with Jira include ability to link back to Aha Item

When configuring sync between Aha and Jira, it should include the ability to have a URL back to the associated Aha idea inserted in Jira field. This would allow Product and Engineering a better way to trace stories back to the original Features, O...
Joe Watson almost 5 years ago in Jira 2 Future consideration

JIRA integration without admin account rights

At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...
Guest over 9 years ago in Jira 0 Already exists

Default JIRA Imports to Parking Lot, when there is no Fixed Version/Release

Regarding importing features into Aha! that are not part of a fixed version in Jira....Today, When you import these features, they will land in the left most active release. If there is not an active release, they will land in the left most parkin...
Josh Tambor almost 5 years ago in Jira 0 Already exists

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

Calculate last active sprint value in aha.io

Hello, since JIRA is emptying the value of active sprint, but not emitting this information via webhook, aha retains last active sprint in active sprint field. Which is cool as this actually enables creating a pivot report that would show backlog ...
Daniel Pokrývka over 2 years ago in Integrations / Jira 0 Future consideration

Filter which JIRA issues get reflected back to Aha!

Aha! allows product managers to stay at the 40k foot level, while JIRA is used by our development team, which means it contains lots of small implementation details. If all the bugs and tasks being logged by my developers in JIRA reflect back into...
Ely Greenfield about 10 years ago in Jira 4 Already exists

Show JIRA import progress in numbers

As a power user, I want the progress to print to the screen in numerals (e.g. "1 of 250 features imported") so that the information prevents me from re-attempting an import. My current workaround: navigate to the Features -> Board and check the...
Guest almost 8 years ago in Jira 0 Unlikely to implement

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 over 2 years ago in Jira 1 Already exists

Aha Integration Status Criteria

In Integration, I am not able to choose which statuses I send and which status changes I do not. Example, captured, i do not want to send, but Aha Integration allows me to send to down stream systems with a blank mapping. Please enhance integratio...
Sasi Ravichandar over 5 years ago in Jira 0 Already exists