|Announced on||Migration starts||Migration ends|
|November 15, 2021||January 10, 2022||March 28, 2022|
Zendesk is migrating the composers in our standard agent interface from the current outdated technology to a newer, more stable and more reliable technology, powered by CKEditor. Composers in the standard agent interface will now adopt the same composer technology that we use in the Zendesk Agent Workspace.
You’ll see the new composer when you add comments to new tickets, existing tickets, and when you make bulk editing changes to tickets. This change doesn’t include the macro editor at this time. However, once a macro is used in a ticket, the formatting changes are applied. You might consider proactively updating your macros to work with the new format when it's released.
This article has the following sections:
What is changing?
As we migrate functionality to CKEditor we’ve noticed some differences in behavior between the current editors in the standard agent interface and the new CKEditor technology. The purpose of this article is to provide you with the differences you might experience once your account is updated with the new technology. Changes the new editor will provide include:
There are only a few differences between how formatting settings interact with each other in the current editors and CKeditor editor, mostly related to how formatting code is managed by CKEditor. Another behavior difference is that we do not support rich-text formatting inside code blocks in CKEditor.
Autoformatting is a feature which allows users to use markdown-like syntax to format content in the editor. For example, a user could type the pound (#) character and then a space, and that line would be turned into a “Heading 1”. In CKEditor, the native Autoformatting command has slightly different triggers than the current editor. See the table below.
For more, see Formatting text with Markdown
In the current editor, images could be resized using the up or down arrow keys on the keyboard. CKEditor doesn’t support image resizing with the keyboard.
Code blocks in CKEditor only support plaintext. Content that is inside code blocks in the current macro editor will be converted into plain text before being inserted into the composer.
In CKEditor horizontal rule elements will always be on their own line. They cannot be inside of other elements. This differs from the current editor where horizontal rule elements can be inside of other elements. See the difference below:
In the current editor, indentation was very flexible and you can indent pretty much anything. In CKEditor, indentation is more strict. For example, in the current editor, you can indent whole blocks of lists. In CKEditor, you can only indent a list item if it is at the same level as a previous list item. In the current editor, you can also indent blockquotes. In CKEditor, you can only indent the text inside of blockquotes.
- Adding text after removing part of a hyperlink creates a new hyperlink. This is expected behavior.
- To type before or after a link, move the caret to the hyperlink boundary, then press the Arrow key (→ or ←) once. The link is no longer highlighted and whatever text you type or formatting you apply will not be enclosed by the link.
- You need to press the Return key three times to escape a code block. The first return is to get to the next line inside a code block, the second return is to allow for a space between two lines inside a code block, the third return will get you out of the code block.
- Using the down arrow to escape the code block is not supported in CKEditor at this time.
Why is Zendesk making this change?
Zendesk is making this change to unify the technology used to power our editing experience. This will enable us to make composing messages and adding ticket comments as easy as possible.
What do I need to do?
You don't need to do anything. If you have a standard agent interface, the migration will be automatically activated in your account. To tell if you have the new composer, you'll see icons for adding hyperlinks and emojis in the composer window.
All accounts will be impacted by this change without exceptions. If you are using the Zendesk Agent Workspace, this migration has already occurred.