Messages from "VCS changes" appear with """

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

Using Cloud and GitHub VCS integration:

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.  

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

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.

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?

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. 

Sergey Merzlov I'd just like to bump this, if you have it on some external ticket system. We still have this on a YouTrack cloud instance.

We are still experiencing random but frequent " from VCS messages, but we've recently also gotten even more garbage from VCS messages, now seeing e.g.: data-vcs-command="true"> sprinkled in a lot. This has made VCS messages annoyingly hard to read, and quite unreliable.

Hi Halvor,

I reproduced both the " and the data-vcs-command="true"> text on a current build.

In my reproduction, it happens when a commit message contains a command for the issue with a # or ^ prefix (a line like #PRJ-1 tag vcs-test) followed by more lines. YouTrack highlights the command when it shows the message, but on the following lines it marks the wrong spot in the text. That cuts through quotes and other special characters and leaves raw markup visible. The commit itself is stored correctly, so the text in the repository is fine. For example, a commit like this:

#PRJ-1 tag vcs-test
Lagt til "if (x > 0)" rundt segment.

shows up in YouTrack with Lagt til "if (x > 0)" rundt segment. on the second line. A shorter second line, such as ok, shows up as oka-vcs-command="true">.

This could well be what you're seeing, and it would also explain why it looks random. As a workaround (UPD: incorrect, ignore), try writing the issue ID without the # or ^ prefix, for example PRJ-1 tag vcs-test. 

I've also updated the initial issue shared here JT-75282 with the details and passed it to the developers. 

Let me know what you find!

Thanks for following up on this Sergey Merzlov! When I try to lookup your documentation I see that you suggest (link) e.g.:

[commit message text] #issueID [command 1] [command 2] ... [command n]
[issue comment text]
...

Or similar but with `^`. But are you saying that command processing also works fine without any of these characters? Or will processing be different in any way? In any case a very simply workaround which we will try!

Hi Halvor,

I need to correct my earlier suggestion. Commands are not processed without the # or ^ prefix. The workaround looked like it worked in my test, but that was a mistake on my side: the command wasn't applied, and I misread that result. Sorry for the confusion.

Without the prefix, YouTrack still attaches the commit to the issue when the ID is in the message, but it doesn't apply the command. So the workaround only suits commits where you need the link to the issue and a readable message. For commits that need to apply a command, keep the documented format. The display problem will remain for those until JT-75282 is fixed.

Let me know if you have any more questions!