PATCH to update issueStatus re-encodes comment text

Crowdin Issues
1

Steps to Reproduce

  1. Create a string comment with quotes in the text, e.g.: Test “quotes”

  2. PATCH the comment to resolve it:

PATCH /api/v2/projects/{projectId}/comments/{commentId}
[{"op": "replace", "path": "/issueStatus", "value": "resolved"}]
  1. GET the comment or observe the webhook payload

Expected

  • text remains:

    Test “quotes”

Actual

  • text becomes:

    Test "quotes"

  • Repeating step 2 causes double-encoding:

    Test "quotes"

2

Hello Gerhard,

Thank you for bringing this to our attention. I suppose it might be related to how the system handles character encoding during updates, but I need to double-check this with our development team.

In the meantime, you may want to avoid using quotes in comments or consider using different characters that do not require encoding.

I will update you once there’s any feedback from the tech team.

1 Like
3

Hi @gerhard

I’ve received an update; it looks like it’s a small glitch.

Our team will fix it (int. task number CN 63041).

Thank you once again for reporting this!

1 Like
4

Thanks for the prompt response. Please let me know when a fix has been deployed so that I can remove the workarounds from our code.

5

Hello Gerhard,

Surely, we’ll keep you informed