You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am successfully using PowerShell Invoke-RestMethod to run jql queries, but when i add a fields list, &fields, or &startAt - the ampersand & does not seem to be getting parsed correctly
This works fine:
$Headers = @{ Authorization = $basicAuthValue }
$Body = @{ jql = "status=Closed" }
$Params = @{
Uri = "https://me.com/rest/api/2/search"
Method = "GET"
Headers = $Headers
Body = $Body
}
$response = Invoke-RestMethod @Params
$response | ConvertTo-Json
But if the jql contains a fields list:
$Body = @{ jql = "status=Closed&fields=project" }
The remote server returned an error: (400) Bad Request.
If I capture the error:
{Field 'fields' does not exist or you do not have permission to view it.}