Automated Integration Migration for Aha! - Jira Server to Jira Cloud
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...
Synchronize logged time and remaining estimates from Jira back to advanced estimates
Using the Enterprise+ Capacity Planning for Teams feature, you can define an advanced estimate on a feature record and send it to the Jira. The total value of the advanced estimate is correctly reflected in Jira. However when the estimate is updat...
Add 2-way integration mapping for release start and end dates
Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Ability to "lock" a custom field, so no user can edit it
Some of our fields in Aha are solely dictated by the field in Jira, for example Status.
Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrite...
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?
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...
Jira Portfolio adds the Parent Link custom field to Jira. Aha! should support mapping this custom field so that the link between a feature and an initiative in Aha! can be reflected into Jira. This field has the custom field type of "com.atlassian...
Support the "links to" field mapping with next-gen templates in Jira
My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates.
Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" f...
Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item.
Example: Support reports a "Support Defect", Dev reviews, changes it...