In the new integrations 2.0 I can't find a way to set the Iteration Path. While I very much appreciate the new functionality in 2.0 that was a very convenient mapping in order to create work items in a specific Iteration Path.
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...
almost 6 years ago
Create AHA reference automatically after import rather than having to 'resend' all data fields back to the place I have imported from.
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?
Allow TFS integration to populate 'Replication steps' for bugs created in Aha
To be able to easily create bugs from within Aha and use the TFS integration to pull across all relevant info from the description field into reproduction steps. After a long investigation by Aha they found that this link was not created as part o...
Allow more than one Salesforce instance to connect to AHA
Usually before you roll out big changes to any Salesforce instance you test this in a Sandbox. We would however like the Salesforce Sandbox connection with AHA to continue to function to further test profile changes and their impact on the AHA con...
Integrations 2.0: Selectable behaviour for importing new records when multiple Aha! products integrate with a single JIRA project.
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...
about 6 years ago