-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Low
-
Component/s: Admin - Settings - Rovo
-
None
-
Severity 3 - Minor
Issue Summary
The acli feedback command fails with Error: failed to send feedback on ACLI v1.3.22-stable. Debug logs reveal the request reaches api.atlassian.com/feedback-collector-api/feedback but returns HTTP 401 Unauthorized with X-Failure-Category: FAILURE_CLIENT_AUTH_MISMATCH. The CLI does not attach user credentials to the feedback request, despite the user being fully authenticated (other commands like acli jira workitem view work correctly using the same session).
Reproduced independently by both customer and Atlassian support engineer confirmed not environment-specific.
Steps to Reproduce
- Install ACLI v1.3.22-stable:
npm install -g @atlassianlabs/acli
- Authenticate successfully:
acli auth login
- confirm authentication works
acli jira workitem view <any-issue-key>
- Run the feedback command:
acli feedback --email 'user@example.com' --summary 'test' --details 'test'
- Observe the error:
✗ Error: failed to send feedback
Expected Results
- Feedback is submitted successfully to the backend api
- User receives confirmation that feedback was sent
- The command uses the same authenticated session that other acli commands use
Actual Results
The command fails with a generic error. Debug logs (ACLI_LOG_LEVEL=DEBUG) show:
POST /feedback-collector-api/feedback HTTP/1.1
Host: api.atlassian.com
HTTP/2.0 401 Unauthorized
X-Failure-Category: FAILURE_CLIENT_AUTH_MISMATCH
{"code":401,"message":"Unauthorized"}
The request is sent without proper authentication credentials. The FAILURE_CLIENT_AUTH_MISMATCH header indicates the auth type sent is not accepted by the endpoint.