Allow integrations such as Jira at the Product Line level
Integrations may be common across products within the same product line. It would save time and the possibility to make setup mistakes if these integrations can be setup one level higher
Support 'parent link' field in Integrations for other issue types.
Aha recently added support for the Jira 'Parent Link' field in Integrations, and this was delivered via this ticket. https://big.ideas.aha.io/ideas/APP-I-7115 Turns out that this integration will only support the Parent Link field for the Initiati...
Ability to customize the hyperlink in the 'Integration' field for Jira integration 2.0
Assume the following are our server urls. Jira server URL - https://stag.external.sample.com/external_path Jira internal server URL - https://jira.sample.com/jira Now, the hyper link on Aha! records should ideally show https://jira.sample.com/jira...
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 see more than the last 200 logs in Aha-Jira Integrations
Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...
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 6 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?