-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jira 2.12.0 can no longer query my Jira Server #372
Labels
Comments
glennsarti
added a commit
to glennsarti/pdk-planning
that referenced
this issue
Aug 20, 2019
Due to AtlassianPS/JiraPS#372 the version of JiraPS needs to be pinned to 2.11.1 to be used for the automation. This pin can be removed once this issue is fixed.
lipkau
added a commit
to lipkau/JiraPS
that referenced
this issue
Aug 20, 2019
6 tasks
Thank you for reporting this. btw: 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. |
lipkau
added a commit
that referenced
this issue
Aug 20, 2019
…iraServerUrl Added check for trailing `/` to be removed from `JiraServerUrl`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #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
Possible Solution
Workaround - pin to 2.11.1 until fixed.
The text was updated successfully, but these errors were encountered: