Closed glennsarti closed 4 years ago
Thank you for reporting this. Fix should come out today.
btw: can I suggest
if ($Issue.Status -in @('In progress', 'Ready for merge', 'Ready for test', 'Ready for ci', 'Ready for review')) { $hash['expectedColumn'] = 'In progress'}
Yeah. It grew organically so it's not quite fully optimised.
Description
I have automation to query my on premises Jira server. It did a basic Jira Issue query https://github.com/puppetlabs/pdk-planning/blob/master/tools/SyncProjects.ps1#L150-L183
However as of Jira 2.12.0 this functionality is silently failing.
Running some debugging I've found the following:
Jira 2.12
Jira 2.11.1
Note the url used:
2.12.0 -
https://tickets.puppetlabs.com//rest/api
2.11.1 -https://tickets.puppetlabs.com/rest/api
Indeed hitting those URLs manually, Jira is throwing a 404 for the double slash URL.
I suspect this is related to https://github.com/AtlassianPS/JiraPS/pull/370
Also no warnings or errors are thrown which is a concern. Surely a 404 should surface something.
Steps To Reproduce
Expected behavior
Should query and return the issues
Screenshots
Your Environment
Name Version
JiraPS 2.12.0