Can I switch back description field renderer from tinyMCE to Wiki-Style w/o being overwhelmed with html code?

[Christian Beck]

We had activated / installed the tinyMCE renderer, but now we want to switch back to the default Wiki-Style renderer. Problem is that if I change the renderer of the description field in the field configuration schema back to Wiki-Style, the description is full of html text and hardly readable any more.

Is there any trick, or any procedure that allows me to change the renderer while maintaining the formatting (as perceived from the user, e.g. in the view issue screen)?

[Dmitry Sytsko · Accepted solution]

Sorry about necroposting, but since tinyMCE plugin is not supported in JIRA5, I use this workaround for migrating from tinyMCE to Wiki-Style render.

So, first backup your jira instance.

Open entities.xml file in text editor and replace

<description><![CDATA[<p
to
<description><![CDATA[{html}<p

and

p>]]></description>
to
p>{html}]]></description>

Change <description> to custom fields you used with tinyMCE rendor.

And also I`ve found, that JIRA stores some issues description in another format, so also replace

"&lt;p
to
"{html}&lt;p

and

/p&gt;"
to
/p&gt;{html}"

Hope it would be helpful.

[Nabil Sayegh]

Unfortunately in 5.1 the format of entities.xml has changed such that the fieldname and the pattern are no longer side-by-side. That makes it much harder to fix with search/replace.

[Nabil Sayegh]

Here's a solution if you have access to the database. But be WARNED! Manipulating the database may corrupt things. There might be trouble with history and cache stuff and your house may burn :-)

USE AT YOUR OWN RISK

0. Backup

1. STOP JIRA

2. UPDATE the table (We use sqlserver, you might need some different concatenation):

UPDATE jiradb_test.dbo.jiraissue SET "DESCRIPTION" = '{html}' + CONVERT(nvarchar(max), "description") + '{html}' WHERE "DESCRIPTION" like '%<%';

3. commit;

4. START JIRA

5. Re-index

P.S.: The module "html" in the system plugin "Wiki Renderer Macros Plugin" has to be enabled for {html} to work. It is disabled by default, because of obvious XSS vulnerability.

[Nabil Sayegh]

Can this be done without export and import?