The URL that is used for integration with our on-prem Jira implementation is not the same as the URL that we use while on our network. Consequently, clickin on the Jira link within any feature takes us to nowhere. This enhancement request is to customize the Jira link format that is used for display (rather than integration) so that Aha users can click on the Jira issue link and have it work.
We have an on-prem instance of Jira successfully integrated with Aha! The integration requires punching a hole in our firewall to allow access from the Aha! cloud. This URL happens to be "https://<external IP Address>/browse/<Jira ID>"
Because of our firewall rules, I can't use this form of the Jira URL from anywhere other than your cloud. Internally, we use URLs that are formed like "https://jira.<ourdomain>.local/browse/<Jira ID>"
I'd love it if I had the option to tell Aha! that it should use the different root URL when *displaying* Jira links in the product. That way I could click on a feature "Integrations: Linked to Issue ..." hyperlink and have it work as intended. Currently, the link goes to our firewall, which dutifully discards the request:-)
|Release time frame|
We would suggest that the best way to solve this issue is by using a split DNS.