You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jira has moved the components from a custom field to an internal field. This happed around 11 days ago 11th of June, 2023.
This has caused New-JiraIssue to fail. The solution was to add a new parameter to function New-JiraIssue in JiraPS.psm1: [Parameter( ValueFromPipelineByPropertyName )] [String[]] $Components,
and further down in New-JiraIssue process section, add the components in a format receivable by the Rest 2.0 API: if ($Components) { $requestBody["components"] = [System.Collections.ArrayList]@() foreach ($item in $Components) { $null = $requestBody["components"].Add( @{ id = "$item" } ) } }
The text was updated successfully, but these errors were encountered:
micheleliberman
changed the title
Creating a new Jira Issue with Components is failing
New-JiraIssue with Components failing from June, 2023
Jun 22, 2023
Jira has moved the components from a custom field to an internal field. This happed around 11 days ago 11th of June, 2023.
This has caused New-JiraIssue to fail. The solution was to add a new parameter to function New-JiraIssue in JiraPS.psm1:
[Parameter( ValueFromPipelineByPropertyName )] [String[]] $Components,
and further down in New-JiraIssue process section, add the components in a format receivable by the Rest 2.0 API:
if ($Components) { $requestBody["components"] = [System.Collections.ArrayList]@() foreach ($item in $Components) { $null = $requestBody["components"].Add( @{ id = "$item" } ) } }
The text was updated successfully, but these errors were encountered: