Issue Summary

When using the Confluence REST API (PUT /wiki/api/v2/inline-comments/{comment-id}{}) to update the resolved status of an inline comment, the API enforces that the version and body fields be included in the payload — even though these fields are not marked as required in the documentation. Additionally, the version number does not increment unless the comment body is also modified, leading to inconsistencies and potential update failures.

Steps to Reproduce

1. Make a PUT request to /wiki/api/v2/inline-comments/{comment-id} with a payload that includes only an incremented version and a change to the resolved field (no change to body value).

Example payload:

{
  "version": {
    "number": 2,
    "message": "Comment resolution updated"
  },
  "body": {
    "representation": "atlas_doc_format",
    "value": "Original comment text"
  },
  "resolved": true
}
 

1. After receiving a successful response, immediately perform a GET request to /wiki/api/v2/inline-comments/{comment-id} to fetch the comment.

Expected Results

• The comment's resolution status is updated.

• The comment’s version number is incremented and reflects the update in the GET response.

• It should be possible to perform subsequent updates using the incremented version.

Actual Results

• The resolution status is updated successfully.

• However, the comment’s version number remains unchanged in the response of the GET request.

• Subsequent update attempts fail with a 409 CONFLICT due to version mismatch.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available