Update Issue Type in Cloud using CLI?

Question

Hey y'all, I realize this seems super easy (as indicated by this old answer I found), but I'm having issues with this.

I'm trying:

./acli.sh --action updateIssue --issue 'ECR-1061' --type "Production Release subtask"

And get:

Client error: 'type' is not a defined field or is not valid in this context (for instance, not being available on the appropriate screen).

Does it matter that I'm on Jira Cloud? Seems like it shouldn't, but thought I'd mention it.

Thanks!

Yoga Reddy {Appfire} · Answer

Hi @Darryl Lee - CCC

Glad that you are able to resolve the issue on your own. To track this issue better, we have created an issue in our Bobswift support portal

Here is the text of our earlier response:

Thank you for opening a support request.

Yes, it should work for the cloud as well. Can you please confirm if you have renamed acli-cloud. properties to acli.properties file and execute the action? If not, please rename the acli-cloud. properties to acli.properties and re-execute the action by appending --debug to the command.

--action updateIssue --issue 'ECR-1061' --type "Production Release subtask" --debug

Please confirm if you are able to set the issuetype "Production Release subtask" from the UI.

Since you are able to resolve the issue, we are going ahead and closing the support request. If you have any questions, please feel free to reopen or add a comment to the support request. We will be happy to reconnect with you!

Thank you!
Yoga

Darryl Lee - CCC · Answer

Oof, found my own answer, although had to take a roundabout route to find it:

I tried to update issue type using ScriptRunner Console.

And got back an error "Only Connect add-on users with admin scope permission are allowed to override screen security."

Which got me to realize that duh, Issue Type was not an an Edit Screen, which makes the error from CLI make all the sense (not being available on the appropriate screen).

Caveat though, once I added Issue Type to the Edit Screen, in the old view I ended up seeing this message below the Issue Type field:
"There are no issue types with compatible field configuration and/or workflow associations.
The issue type can only be changed by moving this issue."

Ugggh, so then, it's a migration issue.

So, the trick then, to changing issue types for 200+ issues? The old Export/Import CSV trick. Worked like a charm:
https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html