keno

I see your point.

Even from that viewpoint, we can "mark" a comment deleted and hide it by default like resolved comment thread of GitHub PR. Doesn't it work?

+1

link: https://support.zendesk.com/hc/en-us/community/posts/1260801882670-Feature-request-Permanent-link-to-a-comment-on-a-ticket

Since human takes editing mistakes.

I definitely want to write a comment on a ticket in raw markdown, not with GUI.

I currently write a response in markdown with emacs, and then paste it to edit area of a ticket, and modify with GUI editor. Ahhhhh...

For example, Slack provides both GUI editor and raw markdown editing. I believe that zendesk should follow this.

Environment: Chrome Version 88.0.4324.150 (Official Build) (64-bit), Linux.

What I Got: When I click "フォローする" button on a ticket, the result seemed not to been saved correctly. I got "Reload site: Changes you made may not be saved." message from chrome when I try to reload the page 30 secs after clicking, and the following was cancelled if I reloaded. I can manage to save the result with the following steps: 1. click "フォローする" button; 2. click "オープンとして送信" button with empty comment. (This is very hacky...)

Expected behaviour: Almost synchronous follow, like "self assign" button of GitHub and "Follow this thread" button of Slack.