Jira

The current JIRA integration Updates feature has limited control capabilities. You can select or ignore items to bring into Aha! The problem is that if you "ignore" a card, it doesn't stick, so any update to the card in Jira mandates that you igno...

When configuring a webook in Jira, there is a checkbox: ☐ "Exclude body" Request with empty body will be sent to the URL. Leave unchecked if you want to receive JSON. If someone accidentally checks that, Aha! won't get any updates. There is no log...

It would be great to be able to easily communicate the rank order of a feature from Aha! to JIRA. If we created a custom field in JIRA for "Aha! Rank" and send the rank over to that field that would be a step in the right direction. Or alternately...

We have Engineers that take the Customer focused epic and break that down into multiple epics (sometimes technical), so we don't want to have them to get out of the tool they work in (JIRA) and switch to Aha!, just to enter the new features for th...

High-level: The URL that is used for integration with our on-prem Jira implementation is not the same as the URL that we use while on our network. Consequently, clickin on the Jira link within any feature takes us to nowhere. This enhancement req...

We currently use Google SSO for our JIRA system. The Aha! integration however requires a username/password user account & not an SSO user. I need to be able to use an SSO user for the integration, since that is the only option that our JIRA ...

Who would benefit? Jira users who would like their development team to see the initiative score. What impact would it make? Clarity on prioritization from a strategic level. How should it work? Allow default scorecard and custom values to display ...

The ability to do a bulk import exists, but if the issue already exists in Aha! it does not re-import. It would be useful to have the ability to alternately do a bulk update. This is particularly useful in the off chance something breaks with the ...

Now that Atlassian has announced that Jira Server will not be supported by 2024, we need to find a way to migrate the existing Aha! - Jira Server integration without having to re-establish the connection. The recommended methods indicated in the l...

From the Jira "READ SECOND" blog post: "If a new issue is created in JIRA that belongs to a record that is already link to Aha!, then the issue will be automatically imported to Aha! This applies to issues created under a version, stories created ...