How to modify WYSIWYG editor in cloud-hosted Jira?

[mhulse]

Hello,

This WYSIWYG editor:

Questions:

1. Is it possible to modify the WYSIWYG buttons? Are they configurable?
2. Is it possible to turn off WYSIWYG mode?
3. Is there Markdown support for cloud-hosted users?
4. Can I modify the keyboard shortcuts?

Thanks for reading.

[Angélica Luz · Accepted solution]

Hi Michael,

Thanks for reaching out to Atlassian Community.
1 - Is it possible to modify the WYSIWYG buttons? Are they configurable?
It's not possible to configure the buttons that appear on the editor.

2 - Is it possible to turn off WYSIWYG mode?
Currently, the new issue view has only this option, if you want to use the old editor, you can disable it by going to your Profile picture > Personal settings > Disable Jira Labs (note that it will not be disabled to Jira Core and Next-Gen projects).

3 - Is there Markdown support for cloud-hosted users?
Currently, markdown is only available for the new issue view, it includes next-gen and business projects. If the Jira Labs is enabled, it will also work for classic projects.

4 - Can I modify the keyboard shortcuts?
This option is also not available.

For the settings that are not available, please feel free to raise a feature request on jira.atlassian.com adding more details about why this would be important for your environment.

Regards,
Angélica

[mhulse]

Thanks for taking the time to reply and help, I really appreciate it!

[Alis-Hathway Ward (DO NOT USE)]

Just an update here for 2.

This setting is now located in:

Profile picture > JIRA: Settings > find the "Labs" toggle.

Note also that (from what I've seen), this doesn't turn it off on next-gen projects. You're stuck with the WYSIWYG there and no obvious way to switch to the standard editor.

[Louter Ezhov]

PLS, give me opportunity switch to SIMPLE MarkDown EVERYWHERE! Your WISYWIG does not work correctly! IT can't paste (and paste doesn't work at firefox) MD as normal text, 'Enter' button works randomly. It's really stupid idea to create yourself WISYWIG (and internet has TOO MAAAANY posts about "Why do not create yourself WISYWIG" and every weak junior (and very strong senior) MUST know it)

Try to use YouTrack when you wanna look "How do it correctly?"

[Lev_Lybin]

I would like also disable only Jira WISYWIG, I use Jira for many years, and don't like Jira WISYWIG.

[Mike Wilde]

The WYSIWYG editor is just horrible... 

[Daniel Dhillon]

@Angélica Luz, is this going to be a future feature since it is beneficial to the users?

[jmgarcia]

+1 to what everyone is saying about the WYSIWYG editor.

[Paul]

+100 or so on disabling the slow and cumbersome MS-Word style editor and ability to go back to markdown that is used by every developer out there.

[Alexey Novikov]

what a steaming pile of brown substance this "better" redesign that enforces wysiwyg is.

[Peter Mullally]

Please make the WYSIWYG editor optional, it's just horrible to use.

[Robert Meffan]

The new editor is terrible. I don't want WYSIWYG / Rich Text, and I absolutely DO NOT want real-time auto conversion of markdown (or wikimarkup). If I wanted a poor UX for editing text, I would use Word. What I and most serious users want is to be able to write and edit comments without having to break our flow to constantly fix the editor's annoying mistakes.

Slack broke their comment editor in the same way you have broken your editor, and it was awful. Fortunately, they listened to their users, and made it possible to disable the wretched thing. I know how Atlassian works, unfortunately, so I know that there's little chance you will listen and give your power users the option to not have to use your equally wretched editor.

Stop trying to help casual or lazy users at the expense of power users. Wikimarkup and Markdown are easy to use and read. Forcing a broken rich text editor on people is terrible UX. If these editors worked properly 99% of the time, they would be still be bloody annoying, but they would at least be tolerable. Yours doesn't work. Every time you "improve" your editors, you make them worse for power users.

Every. Single. Time.

[Henning Peters]

This WYSINWYW (what you see is not what you want) editor might be ok for non-technical users, but any developer is struggling with things like this.
I cannot add any tables from mysql-console output as a jira table (had nice formatting with "|" ), it gives me headaches to insert code-snippets or something. It feels like "turn the 2nd-leftmost key into position 3 on the right panel to activate the turning signals" in my car...
Please give us back the old "source" editor.

[Vadim Kapitanov]

+1 for allowing to disable WYSIWYG. I can use plain text when creating a task, but editing the one I just created - I have to suffer. >.<

[Roby Van Hoye]

+1 on bringing back the option to have a simple text-field with MD

[Stefan Girlich]

+1  The new editor takes away all the flexibility I always appreciated about the classic markup editor. Please bring it back as an option; having to use the current WYSIWYG mode is very frustrating.

[juan]

This answer is no longer valid.

The personal settings page says: "We're currently transitioning everyone to the new issue view, so you're no longer able to switch back to the old issue view.".

Please provide a valid answer.

[Stephen Ball]

The new WYSIWYG editor is awful, give me a way to disable it so I can curate my stories outside of JIRA in a text editor using markdown and just paste them in without random bit turning into blocks of code with no way to turn them back to normal text

[Илья Богунов]

+1 can't even import issues from jira, cause every formatting brakes completly.
So you have to MANUALLY edit all the issues.

[Виталий Ковалёв]

You implement community discussions and `Like`s and then act against clear results.

The only way WYSIWYG can't be disabled is because it cannot be converted to plain markdown which means it's badly designed.

That's just wrong, Atlassian.

[Timothy Harding]

I too am finding the wysiwyg editor very difficult to use and prefer markdown. I am unable to create collapsible code fields which make reviewing stack traces very difficult. Please bring back the source button.