Jira

The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested. In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...

I have created a custom field in Aha which maps directly a field in Jira. I have created a pre-defined choice list in Aha! which contains all possible values in Aha!. When creating the integration between Jira and Aha! I have to manually match eac...

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...

I spend countless hours trying to debug webhook issues only to find the error should have been easily caught and reported back correctly. It seems the only issue that comes back is "Processing webhook: unhandled error. Please contact support@aha.i...

After I have imported a record from Jira I then have to ‘resend all the fields’ from AHA in order for the AHA reference to be populated. Is there anyway that on import an AHA reference is created at that point?

Often teams will integrate multiple Aha! products with a single JIRA project. Currently the import behaviour in 2.0 is you get 'n' number of import candidates which appear in the "Import New Records" modal for all integrated Aha! products regardle...

Would like to be able to view the sprint a feature is currently assigned to in JIRA. It looks like we have most of the other fields available for mapping but that one isn't available. I get a ton of questions about when a feature is scheduled to b...

One of the fields we have in JIRA has over 100 values. Mapping each value to Aha is a no go. The interface to manually drag and drop each value to the correctly mapped value is slow, cumbersome and took over 60 seconds to just do 1. It will be pr...

In 1.0 you could map Features to Stories but also set the JIRA integration to support importing unmapped types. This meant that bugs, tasks, etc created in JIRA could be imported as Features in Aha! This is important, without this we have no way t...

JIRA has a custom field type that supports cascading. This is a very useful field type that is currently not supported in Aha. Due to this, we cannot make the field required in JIRA and thus compliance drops off. The JIRA API supports this field s...