Ability to Disable Rich Text Comment Editor in Jira Cloud

[Kevyn Weiner]

It appears that JIRA Cloud recently gained an in-line Confluence-style text editor bar for comments, so that users' don't have to remember \{noformat\} and such.  That's wonderful, except that the comment field often intercepts my attempt to switch Chrome tabs (CTRL-1, CTRL-2, etc), and instead inserts h1. and h2.

Is there any way to do the following:

1. Disable the comment rich text editor, without disabling Wiki rendering?
2. Disable the comment rich text editor, just for my user?

It's a nice addition, and one that I think my users' will appreciate, but I would very much like to opt my own user out of using it, and instead go back to using wiki markup code.

Thanks!

[Paulo Junior · Accepted solution]

Hi Kevy,

It's not possible to disable the rich text without disabling the wiki rendering, however, to stop inserting headers on comments when trying to switch to other tabs, you just have to click outside of the comment box before.

Kind Regards,

Paulo.

[Kevyn Weiner]

Thanks for the answer, Paulo! Hopefully the ability to enable/disable the rich text edit box per-user comes in a future version.

[Charles Jean-Baptiste II]

I agree, please allow for the enabling/disabling of the rich text edit box.  I was use the manual disabling of the rich text.

[Connor Crothers]

"It's not possible to disable the rich text" is not an acceptable answer.

The new editor makes comments vary more difficult to manage, format, and in some cases, impossible, depending on your goal. I'm all for new features, but not at the expense of old ones.

Please do no force all users on March 31 to have to use the new view.

https://i.ibb.co/2jcbgPJ/image.png

^ this view is garbage

https://i.ibb.co/NrHkgBd/image.png

^ the markup view is far better and is standard (to at least some degree) in across most platforms.

[John Rocha]

Add yourself to the Atlassian bug report for this problem

https://jira.atlassian.com/browse/JRACLOUD-72631

[Connor Crothers]

Wiki markup should not be removed. WYSIWYG editors are cumbersome, break any text pasted into them, require a bunch of extra clicking, require everyone to learn new things, prevent compatibility with editing past comments, are terrible at rendering images in a clean compact way, and the list goes on.

See this man's comment on some of his own annoyances in the same link you provided earlier.
https://community.atlassian.com/t5/Jira-Core-questions/How-do-I-use-Jira-Wiki-Markup-in-new-rich-text-editor/qaq-p/1020018#bodyDisplay_34875f256490b9

The rich text editor NEEDS to be configurable per user to people can effectively and productively do their jobs. I only hope that the JIRA team will do theirs by not forcing the new WYSIWYG editor on us.

[Joe Sparks]

This is unacceptable.  The WYSIWYG editor is junk.  It adds in tons of extra lines between things and makes lists and numbered lists look horrible.  At least with the ability to switch between markup and WYSIWYG, you can make everyone happy and want to use the software.  Now, I am being FORCED to switch to the new issue style and LOSING functionality.

Atlassian really needs to take a closer look at what their customers want and quit removing features that people depend on.

[John Rocha]

There is an Atalassian ticket for this.

https://jira.atlassian.com/browse/JRACLOUD-72631

You can vote for it and add your comments there for the devs to see. 

[T Chambers]

FYI, Jira Wiki Markup is no longer supported in the cloud. See https://community.atlassian.com/t5/Jira-Core-questions/How-do-I-use-Jira-Wiki-Markup-in-new-rich-text-editor/qaq-p/1020018#U1208535

[Paul T]

Thank you for sharing, @T Chambers

Atlassian, that's a mistake!

[T Chambers]

All, adapting here what I said at https://community.atlassian.com/t5/Jira-Core-questions/How-do-I-use-Jira-Wiki-Markup-in-new-rich-text-editor/qaq-p/1020018#U1208535, I thought it was a mistake until I copied the text from Jira's rich text editor into a Google Doc and was pleased that the rich text is preserved. As long as I can export this easily, I don't miss the markup language. It was different between Jira and Confluence and IIRC neither was fully compatible with "official" Markdown (markdownguide.org) anyway. Good riddance. Good job, Atlassian, this is progress!

Also @Paul T you may have already noticed, but vestiges of markup are still around in history (read-only), modals (still editable), and maybe some other places. I wonder if Atlassian plans to clean it all out completely.

[Zack Maxwell]

oh the horror. Jira used to be good for developers