Skip to Main Content
Status Shipped
Categories Jira
Created by Guest
Created on Oct 20, 2015

Allow customization of on-prem Jira link displayed in Feature details so that link actually works


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:-)

    Mar 9, 2021

    It is now possible to specify an internal URL for on-premise Jira integrations.

    Within integration settings, select the Configure account step and update the Internal server URL field.

    This URL will be used for the Jira URL in each linked record so that users can access the Jira issues from inside your firewall.

  • Attach files
  • Jor Bratko
    Dec 18, 2020

    Split DNS isn't a good answer for us either. Security wants to use an allowlist for incoming IP addresses and this model makes that list too big to manage.

  • Miguel Bracchini
    Apr 8, 2016

    Ben down that path... Unfortunately that is not an option.   Our public IP is not constant. It is Amazon Elastic Load Balancer. Even if we set it up with current IP, it is bound to break.

  • Miguel Bracchini
    Feb 29, 2016

    Need it as well!