I was using the renderer FckEditor in Jira 3.5, and I had to switch to JEditor when I upgraded to 6.1.
For most of the fields, the rendering is correct, but in some cases the html tags are escaped (for example <br/> becomes <br/>). Therefore the tags are visible in the rendered view.
Anybody knows why it happened? And why it only happened in some places?
Please check that Enter mode is set to Paragraphs in JEditor Configuration.
There's also a known bug where JEditor decides to render a field using wiki renderer. In this case wiki renderer encodes tags and tags become visible. This problem is already fixed, the fix will come with JEditor 1.5.48 (next release).
We were using Jira 3.5 with Fckeditor, and when we migrated to Jira 6.1 and JEditor, that rendering problem appeared on some issues. When creating new issues there is no problem.
I know that some users used to copy from word into fckeditor, so it may be the reason why only some fields have rendering problems.
One possibility is to copy the content of the rendered view into the source view, but the problem is that there are thousands of fields with that problem. Do have an idea about how I could fix all the problematic field quicklier?
The problem is clear now.
When JEditor renders fields it decides if the contents are html formatted or wiki formatted (wiki text can contain html). It looks like for some code created by FCK JEditor makes incorrect decision.
The simplest way to fix this on your side is to update all of these fields in DB wrapping content into <div> ... </div> tag. This will force JEditor to render as html.
On our side we can change the patterns used to decide if the content is html.
If you start editing an issue where tags are visible and save it with JEditor the issue will be stored like this in DB. If you already saved this issue before then wrapping with <div> tags won't help.
However other issues should be fixed, try checking them.
If this problem persists in all issues please check the html in DB, there should be no encoded tags (like < and >).
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs