I have 2 connectors in the Stash server.xml.
First is the standard connector, but on port "7991". This is intended for the localhost trused applicaiton linking between Jira and Stash. If I also log in using this port I can view the Jira issue popup fine from the commit screen in a Stash repository.
The second connector, on port "7990", has proxyName and proxyPort values. I am proxying through IIS using ARR. Through the proxy when I click an issue I get a "Page not found" dialog box.
If I right click the issue link and open in a new tab the Issue opens correctly in Jira (the link is also through the proxy).
So far everything else in Stash and Jira seems to work through the proxy.
Turns out it was the Inbound URL Rewrite Rule on IIS. The "jira" rule was finding jira in the url then forwarding the request to Jira and not stash.
The URL for the issue is http://xxx/stash/rest/jira/latest/issues?issueKey=xxx--nn. By changing the regex pattern to ^jira/(.*) it now behaves as expected.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot