New-JiraIssue @parameters -Credential $Creds Invoke-JiraMethod : Issue Does Not Exist

[sysadmin24]

Description

Module has been running fine up until we updated Jira to 9.4.3.
Now when we try to create a new issue it can't recognize the issue types at all. I've tried them all.

New-JiraIssue @parameters -Credential $Creds - -- Invoke-JiraMethod : Issue Does Not Exist

Steps To Reproduce

Create a new ticket and this message comes up.
Tried with no issue type, any issue type that came up in the get-issuetype list, and IssueType = "", but none work.

Expected behavior

Ticket should be created.

Screenshots

New-JiraIssue @parameters -Credential $Creds
Invoke-JiraMethod : Issue Does Not Exist
At C:\Users\markladmin\Documents\WindowsPowerShell\Modules\jiraps.2.14.6.old\JiraPS.psm1:2012 char:19

•     $result = Invoke-JiraMethod @parameter
  

•               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidResult: (:) [Invoke-JiraMethod], RuntimeException
  • FullyQualifiedErrorId : InvalidResponse.Status404,Invoke-JiraMethod

Please assist if possible.

[Rogueit]

Generally when I get issue does not exist, its because something is wrong in my $cred variable.

Here is how i creating my cred

$reporter = "[email protected]"
$API = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
$PWord = ConvertTo-SecureString -String $API -AsPlainText -Force
$Cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $reporter, $PWord

[borix]

This may be related to the createmeta REST endpoint being removed in version 9.x:

Createmeta REST endpoint to be removed

This module would have to be updated to use the new endpoint.

[rnelson0]

There have been no new releases since 2020, is Atlassian looking into a new release? I know I can probably figure out how to assemble a copy of the latest code manually, but I can't even tell if this is fixed in HEAD, much less distribute any such fix to coworkers.

[claudiospizzi]

Same issue here. Is related to the change @borix mentioned.

We've created a workaround for our use case, and we use this internally. Not sure if this covers all cases and if it is a complete workaround. Anyway, if someone finds that helpful:
arcadech@5d28053

[ChefkeGremmen]

@claudiospizzi ; thank you so much for this. I hope the maintainers find room to get the CICD pipeline up and running again so your pull-request can get processed. Your change fixed our situation.