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?
Check following answer
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
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:
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.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot