JiraPS icon indicating copy to clipboard operation
JiraPS copied to clipboard

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

Open sysadmin24 opened this issue 2 years ago • 6 comments

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.

sysadmin24 avatar Feb 21 '23 19:02 sysadmin24

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

Rogueit avatar Mar 09 '23 19:03 Rogueit

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.

borix avatar Mar 22 '23 19:03 borix

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.

rnelson0 avatar Aug 07 '23 12:08 rnelson0

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: https://github.com/arcadech/JiraPS/commit/5d2805357475c4564ef013d4a36e497d23f68595

claudiospizzi avatar Nov 13 '23 22:11 claudiospizzi

@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.

ChefkeGremmen avatar Mar 19 '24 07:03 ChefkeGremmen