ACLI: All jira workitem commands fail with "unexpected error" while REST API works

[Giuseppe Vincenzi]

Problem

All "acli jira workitem" commands fail with generic "unexpected error, trace id: XXX" while the same operations work perfectly via direct REST API calls using identical credentials.

Environment

- ACLI Version: 1.3.11-stable and 1.3.13-stable (both affected)
- OS: Linux (tested on WSL2 and Docker containers)
- Auth Type: api_token

Steps to Reproduce

1. Authenticate: acli jira auth login --site MYSITE.atlassian.net --email EMAIL --token
2. Verify: acli jira auth status Shows "Authenticated"
3. Run any query:
- acli jira workitem view ISSUE-123 --json 
- acli jira workitem view ISSUE-123 
- acli jira workitem search --jql "key=ISSUE-123"
- acli jira project list --recent 5

All return: Error: unexpected error, trace id: XXXX

Proof that REST API works

Using the same credentials with curl:

curl -u "email:token" "https://MYSITE.atlassian.net/rest/api/3/issue/ISSUE-123"
Returns full JSON (56KB) - WORKS

curl -u "email:token" "https://MYSITE.atlassian.net/rest/api/3/myself"
Returns user profile - WORKS

Conclusion

- Authentication works
- Credentials have correct permissions
- Direct REST API works perfectly
- ACLI fails on ALL query commands

This appears to be a bug in how ACLI handles API responses.

ACLI is completely unusable for any Jira operations. We have CI/CD pipelines depending on it.

[Giuseppe Vincenzi · Accepted solution]

Update: Retested and the issue is now resolved. All acli jira workitem commands are working correctly. Thanks for the fix!

[Rob Taylor]

I have the same issue.

There's another report here

https://community.atlassian.com/forums/Jira-questions/Bug-acli-jira-workitem-create-fails-with-unexpected-error-trace/qaq-p/3183142