Messages from "VCS changes" appear with """

Messages that appear under "VCS changes" appear to randomly include " instead of the " sign. We've found no particular pattern to the occurrences. What could be causing this?

1
8 comments

For any support team, I've shared a couple of examples with Upload ID: 2023_05_30_Xfjev6GXdA1raDdVtMHqpd

0
Hi!

I'm Sergey from the YouTrack team.

I've run a few tests and not managed to reproduce anything similar so far. What's your exact YouTrack version (either under the question mark at the top right corner or footer in older versions)?
0

Using Cloud and GitHub VCS integration:

Build 2023.1.10106
Monday, May 29, 2023
 
The issue has been experienced after the date above.
0

Thanks.

Please copy the whole message from the GitHub's webhook payload (Repository's Settings → Webhooks → Recent deliveries). It should be something like 

"message": "DO-167\n\n* Valgbar \"reply to\"",

Please paste it as is in the code block here. Thanks.  

0

Had to do another more recent commit. Here is the webhook message:

      "message": "#ODX-1316 Til info\nLagt til \"if (cm.getAmount() > 0)\" rundt det Robert mener er relevant segment.",

Upload ID for screenshots: 2023_06_01_WzxgYTVhDrKvM1oeKnmbY1

0

Thanks for the details.

I've created a corresponding issue in our public tracker: https://youtrack.jetbrains.com/issue/JT-75282/Quotes-in-commits-are-displayed-as-quot-in-some-cases. Please feel free to vote for this issue. This helps us measure how many customers encounter this problem, and you’ll also get subscribed to the issue’s notifications. To do so, sign in to JetBrains YouTrack and hit the thumbs-up icon.

0

Thanks Sergey Merzlov, will do. Out of curiosity, were you able to reproduce, or is there something still unknown in our setup that is causing this?

0

As you mentioned yourself, it doesn't reproduce with all the cases where quotes are used. Outside of your examples, I managed to reproduce a similar issue with one rather peculiar case. As for why and how it is reproduced, we need to investigate it further; hence I created a corresponding bug report. 

0

Please sign in to leave a comment.