Using the Jira Command Line Interface to create an issue with a multi-line description

Question

I am using a PowerShell script to read in issue details like Summary and Description. For each PSObject in my array I want to call the acli.bat to create an issue. Everything works except for multi-line descriptions. Only the first line is ever output to my generated ticket. Here is a code sample...

Import-Csv -Path ".\issues.csv" | ForEach-Object {
    .\acli.bat --action createIssue `
        --server "$server" `
        --user "$user`
        --password "$password`
        --project TEST `
        --type Task `
 --summary $_.Summary `
        --description $_.Description `
}

While I have used runFromCsv in other projects to import tickets, even those with multiple line descriptions, I do not want to directly runFromCsv in this case as I need to make modifications on the fly.

How do I do this?

I am using Jira Software (Server) 8.5 and the Atlassian CLI 9.2

Michael Kuhl {Appfire} · Answer

I'm glad you found a solution. Understand about the file IO.  RunFromCSV or Run with a file containing a line for each action is the supported method, but I understand that won't work for you.

Ryan_Taylor · Answer

I have found a solution.

* Write the description to a file
* Replace --description $_.Description with --file ".\desc.txt"
* Ponder other mysteries of the universe

The full setup is then

Import-Csv -Path ".\issues.csv" | ForEach-Object {
    $_.Description | Set-Content -Path ".\desc.txt" -Encoding "UTF8"
    .\acli.bat --action createIssue `
        --server "$server" `
        --user "$user`
        --password "$password`
        --project TEST `
        --type Task `
 --summary $_.Summary `
        --file ".\desc.txt
}

This add a fair bit more file I/O to my operation as we write this for every record we're making and I have hundreds of tickets to make (porting). I'll need to do this for comments too assuming the --file method works on comments.

Ryan_Taylor · Answer

Unfortunately that does not work. I also tried "$($_.Description)" with no success.