The recommendation of keeping Status as a one way sync from Jira makes Aha! reports silently unreliable, as Aha! and Jira status will diverge if somebody touches a record "by mistake".
If I set it to two-way sync, transitions not allowed by Jira m...
Daniel Hirschberg
about 5 years ago
in Jira
1
Shipped
I have JIRA linked with Aha! and can see the JIRA Id and key - which is great. But I would love to have the URL link available in my list report as well. It looks like there is a field JIRA URL, but it is blank. What is it used for?
We often get a lot of Slack updates as someone is editing a feature. It would be useful to introduce a small amount of delay to the process to allow these edits to be merged into a single update. For us removing the duplicate updates is probably m...
John Biltcliffe
over 5 years ago
in Slack
0
Shipped
My company, as well as many others, does not want to open ports in the firewall to connect to Jira. We use EAA as our protection in front of our on-prem Jira. Aha! supports OAuth to Jira, which is ok but we still need cert-auth in front of that to...
Converting requirements to features after integration
Converting a requirement to a feature will cause the record to lose some custom field information because features may not have the same custom fields. We can choose whether or not to proceed. There's no mention of integration to an external syste...
Add integration from Aha field to Preliminary Estimate field in Rally
I would like to fill out a T-shirt size estimate in Aha, and when I send to the Rally integration I'd like it to populate in the Preliminary Estimate field. Currently I do not have that ability in my integration mappings.
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...
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...
John Paul Grippa
almost 7 years ago
in Jira
0
Shipped
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?