-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
The textarea type attribute in assets stores content in HTML format with CSS styling for formatting. However, if a user copies data from Jira issues text area field that uses wiki format, they need to convert this wiki format into HTML before saving the data in the assets textarea attribute.
The transformed HTML typically uses basic HTML formatting, which may not render correctly in Confluence when using the assets macro.
Transformed simple HTML:
<p>ecos sticks</p><p><font color="#de350b">in rot </font></p><p><ins>oder Unterstrichen</ins></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p>
HTML format accepted by Confluence/assets:
<p>ecos sticks</p><p>Color: <span style="color:hsl(0, 75%, 60%);">in rot </span></p><p><u>oder Unterstrichen</u></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p>
The request is to support simple HTML tags in assets and assets macros for Confluence to steam-line the customisations.
- links to
[JSDSERVER-16316] Assets macro for confluence can not render simple HTML tags
Support reference count | New: 1 |
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 1040282 ] |
Description |
Original:
The textarea type attribute in assets stores content in HTML format with CSS styling for formatting. However, if a user copies data from Jira issues that use wiki format, they need to convert this wiki format into HTML before saving the data in the assets textarea attribute.
The transformed HTML typically uses basic HTML formatting, which may not render correctly in Confluence when using the assets macro. *Transformed simple HTML:* {code:java} <p>ecos sticks</p><p><font color="#de350b">in rot </font></p><p><ins>oder Unterstrichen</ins></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p> {code} *HTML format accepted by Confluence/assets:* {code:java} <p>ecos sticks</p><p>Color: <span style="color:hsl(0, 75%, 60%);">in rot </span></p><p><u>oder Unterstrichen</u></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p>{code} The request is to support simple HTML tags in assets and assets macros for Confluence to steam-line the customisations. |
New:
The textarea type attribute in assets stores content in HTML format with CSS styling for formatting. However, if a user copies data from Jira issues text area field that uses wiki format, they need to convert this wiki format into HTML before saving the data in the assets textarea attribute.
The transformed HTML typically uses basic HTML formatting, which may not render correctly in Confluence when using the assets macro. *Transformed simple HTML:* {code:java} <p>ecos sticks</p><p><font color="#de350b">in rot </font></p><p><ins>oder Unterstrichen</ins></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p> {code} *HTML format accepted by Confluence/assets:* {code:java} <p>ecos sticks</p><p>Color: <span style="color:hsl(0, 75%, 60%);">in rot </span></p><p><u>oder Unterstrichen</u></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p>{code} The request is to support simple HTML tags in assets and assets macros for Confluence to steam-line the customisations. |
Description |
Original:
The textarea type attribute in assets stores content in HTML format, and Jira applies CSS styling for formatting. However, if a user copies data from Jira issues that use wiki format, they need to convert this wiki format into HTML before saving the data in the assets textarea attribute.
The transformed HTML typically uses basic HTML formatting, which may not render correctly in Confluence when using the assets macro. *Transformed simple HTML:* {code:java} <p>ecos sticks</p><p><font color="#de350b">in rot </font></p><p><ins>oder Unterstrichen</ins></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p> {code} *HTML format accepted by Confluence/assets:* {code:java} <p>ecos sticks</p><p>Color: <span style="color:hsl(0, 75%, 60%);">in rot </span></p><p><u>oder Unterstrichen</u></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p>{code} The request is to support simple HTML tags in assets and assets macros for Confluence to steam-line the customisations. |
New:
The textarea type attribute in assets stores content in HTML format with CSS styling for formatting. However, if a user copies data from Jira issues that use wiki format, they need to convert this wiki format into HTML before saving the data in the assets textarea attribute.
The transformed HTML typically uses basic HTML formatting, which may not render correctly in Confluence when using the assets macro. *Transformed simple HTML:* {code:java} <p>ecos sticks</p><p><font color="#de350b">in rot </font></p><p><ins>oder Unterstrichen</ins></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p> {code} *HTML format accepted by Confluence/assets:* {code:java} <p>ecos sticks</p><p>Color: <span style="color:hsl(0, 75%, 60%);">in rot </span></p><p><u>oder Unterstrichen</u></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p>{code} The request is to support simple HTML tags in assets and assets macros for Confluence to steam-line the customisations. |
Description |
Original:
The textarea type attribute in Jira stores content in HTML format, and Jira applies CSS styling for formatting. However, if a user copies data from Jira issues that use wiki format, they need to convert this wiki format into HTML before saving the data in the assets textarea attribute.
The transformed HTML typically uses basic HTML formatting, which may not render correctly in Confluence when using the assets macro. *Transformed simple HTML:* {code:java} <p>ecos sticks</p><p><font color="#de350b">in rot </font></p><p><ins>oder Unterstrichen</ins></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p> {code} *HTML format accepted by Confluence/assets:* {code:java} <p>ecos sticks</p><p>Color: <span style="color:hsl(0, 75%, 60%);">in rot </span></p><p><u>oder Unterstrichen</u></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p>{code} The request is to support simple HTML tags in assets and assets macros for Confluence to steam-line the customisations. |
New:
The textarea type attribute in assets stores content in HTML format, and Jira applies CSS styling for formatting. However, if a user copies data from Jira issues that use wiki format, they need to convert this wiki format into HTML before saving the data in the assets textarea attribute.
The transformed HTML typically uses basic HTML formatting, which may not render correctly in Confluence when using the assets macro. *Transformed simple HTML:* {code:java} <p>ecos sticks</p><p><font color="#de350b">in rot </font></p><p><ins>oder Unterstrichen</ins></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p> {code} *HTML format accepted by Confluence/assets:* {code:java} <p>ecos sticks</p><p>Color: <span style="color:hsl(0, 75%, 60%);">in rot </span></p><p><u>oder Unterstrichen</u></p><p>oder <b>auch fett</b></p><p><a href="http://google.com" class="external-link" target="_blank" rel="nofollow noopener">link title</a></p>{code} The request is to support simple HTML tags in assets and assets macros for Confluence to steam-line the customisations. |