Some of the Jira instances we connect our Stash instance to are sometimes unreachable (due to downtime, network issues etc).

When we attempt to navigate to a Jira issue on the Commits page (i.e. through /plugins/servlet/jira-integration/issues/jira-id), we would get a skull error:

Connection lost with name of Jira instance

This error message is received irrespective of whether the Jira id in question is hosted on the unreachable Jira environment. The Jira id in question may actually be hosted on a perfectly reachable Jira instance.

Can this be improved somehow? For example, in resolving the Jira id visit all Jira instances and remember their reachability and only return the skull error when all instances have been exhausted. Or, allow projects/repos to have 'preferred' Jira instances to visit first.