Move to Rich Text Editor (Jira) from Jeditor by Bobronix

[Frank Racioppi]

Our instance has been running Jeditor for several years (10's of thousands of active issues). We would like to convert away from Jeditor, in particular in the description field, but changing the renderer leaves us with residual markup language (e.g. <p> <br>). Is there anyway to go back, or are we stuck with Jeditor for the rest of time? 

[Radek Janata · Accepted solution]

Hi,

I was dealing the same couple months ago when I was migrating whole instance with jEditor installed to another Jira instance where common Jira wiki only was enabled. jEditor was enabled for Description field, many other fields and all comments.

It was pretty tough but the migration was very successful at the end and no one would even recognize that jEditor is no longer installed on the target instance :) Even those specific jEditor panels have been successfully migrated to corresponding wiki syntax.

I used Graham Hannington's "Wikifier" solution. I adjusted original XSLT and added dozens of new items to describe original jEditor's specific objects. So all thanks come to him :)

While Graham's solution focuses on transforming Confluence XML to Wiki markup, it works pretty well for transforming general HTML into Jira Wiki (Rich Text Editor) markup.

Get inspired here:

• http://www.amnet.net.au/~ghannington/confluence/wikifier/
• http://www.amnet.net.au/~ghannington/confluence/readme.html

In my case, I parsed and replaced the whole exported entities.xml before the import to the target instance.

In your case, you might want to prepare similar solution and utilitize this via REST API or update description / comments directly in DB (while having Jira shut down). Be careful and test thoroughly on a testing environment, of course.

Regards,
Radek

[camus_b_li]

Thanks for the link: http://www.amnet.net.au/~ghannington/confluence/wikifier/

For me, I have to manually modify the result to convert <img>.

[Justin Alex Paramanandan]

Updating the link to the README here: http://www.amnet.net.au/~ghannington/confluence/readme.html

[Radek Janata]

Thanks for pointing out the incorrect link, I've fixed it in my answer, too.

[Christopher Watkins]

Dear Radek,

Thank you for sharing this.  I'm looking to do exactly the same as you, i.e. export issues from a JIRA instance that used JEditor into a new instance that will use the wiki render.

You mentioned above that you modified Graham Hannington's solution.  Would you mind sharing your modifications please?

Thank you,

Chris.

[Dimitri Cools]

same here .. I 'm feeling the same pain !!

any tips welcome .. (this is a nightmare)

[Derek White]

Contact JEditor support, they have private scripts they can provide to convert it all.

Supports multiple dbs, converts images to attachments properly, etc.

Can even be run on single projects (disable jeditor for a single project, convert the project, and now you have a single project test run completed and ready for UAT).

Their support has been quite helpful.

[Derek White]

BTW, it converts to modern Atlassian wiki-style (RTE is old-school).

[Derek White]

If you used it with custom fields, after converting, be sure to change the Renderer in the Field Configuration(s). It will be set to the basic text Renderer, flip it to the wiki Renderer and save. I believe Description and Comments did this automatically, but check them while you are in there.

[francis]

Check following answer

https://confluence.atlassian.com/jirakb/how-to-enable-html-in-jira-text-fields-771895067.html

The steps to address this problem is

* Enable html support in the wiki renderer

* Convert the jeditor fields to wiki renderer (in the field configuration scheme)

* run a query in the database to convert all jeditor to something like 

{html}

<original content>

{html}

[Justin Alex Paramanandan]

The suggestion to enable the html macro on the Wiki Renderer is a bad idea.

You'll be opening up your instance to malicious code being added to the environment at any point.