Dear all!
I am open source developer of one of the most popular addon-ons for JIRA, which is JIRA Syntax Highlighter.
I just found out, that the new Rich Text Editor introduced by JIRA 7.2 as a Labs feature is completely breaking my plugin.
If you add a code section, it uses JIRA standard syntax module for rendering in the Rich Text Editor instead of the enhanced layout provided by JIRA Syntax Highlighter. And it also doesn't support any of the new capabilities like line numbering, highlighting, title etc. And most important, you can also not edit existing code blocks, because the editor thinks, that this is a table and not a code block.
Actually I am surprised that Atlassian is not seriously taking care about compatibility of Rich Text Editor with JIRA Syntax Highlighter. It is 1st or 2nd popular add-on for JIRA for years now and referenced on the landing page of Atlassian Marketplace. Also back in Nov 2015 Atlassian contacted me proactively that they are planning to introduce a Rich Text Editor for JIRA and that my plugin might be somewhat effected. And in 2014 Atlassian contacted me to convince me to make my plugin also compatible for JIRA Cloud, because customers marked my plugin critical for a migration from JIRA on premise to JIRA cloud. So, they are aware of the plugin.
I don't know, what to do now.
Maybe we all together can convince Atlassian, that they need to take care about supporting JIRA Syntax Highlighter properly in the Rich Text Editor approach.
Best regards
Holger
P.S. If you don't activate Rich Text Editor, there is no problem. That's why I marked the plugin to be compatible with JIRA 7.2 on the Atlassian Marketplace.
Community moderators have prevented the ability to post new answers.
Hi Holger Schimanski,
I've seen the issue raised in the Rich Text Editor project https://ecosystem.atlassian.net/browse/JRTE-25. Let's move the communication there as we'll post further updates in the issue comments. Additional bonus would be - that you can track actual status of it with JIRA.
Thanks!
Cheers,
Ignat.
I am working now on compatibility with Rich Text Editor, because Atlassian clearly stated that they will team up with myself to do necessary implementation.
I have done first steps, but I am now running into issues with the local development environment, where Rich Text Editor does not work as expected. See here https://ecosystem.atlassian.net/browse/JRTE-33 for details.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I decided to discontinue development of JIRA Syntax Highlighter.
There are significant efforts needed and too much new concepts to understand and work with to make JIRA Syntax Highlighter compatible with Rich Text Editor introduced in JIRA 7.2 resp. 7.3. This is beyond what I can provide in my spare time as open source developer. I didn't found fellows jumping in to suport me also Atlassian actively decided to not help this open source plugin.
After lots of discussions and complaints Atlassian has decided to improve JIRA standard syntax highlighting by adding support for additional languages.
See here for details. https://jira.atlassian.com/browse/JRASERVER-21067
Best regards
Holger
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
See Ignat's answer. The issue is tracked under https://ecosystem.atlassian.net/browse/JRTE-25
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We do not generally test compatibility with 3rd party plugins, even popular ones.
Any incompatibility is likely to be an accident that the RTE's author is completely unaware of. I'll reach out to the editor's authors to see if they know what's going on and/or can help you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Community moderators have prevented the ability to post new answers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.