I don't see how any sort of markup addresses the use case of the original ticket.

We too receive HTML from various sources, that finds its way into ticket descriptions and comments (often by import).

So it needs to be rendered....

I am resolving this issue as a duplicate of JRA-1585 as this should solve the vast majority of cases where people wish to use HTML. Also ther is a HTML macro that allows users to enter HTML (though this is disabled by default for security reasons).

Alternatively, a HTML render could be created.

Absolutely would love Confluence markup. Everyone here has gotten very used to this, and the transition would be really easy.

I agree that as users comment on issues they should have the ability to mark up the content.

Eighter UBA or HTML support needs to be added to the core of JIRA and not have to rely on another product (Confluence)

ANYTHING is better than just plain text.

As defined in the duplicate issue JRA-3327 - rather than entering raw HTML, I would prefer it to be in confluence style coding to enable the varying output types (pdf, xml, html, any that are added in future (eg: word/excel)).

Just having raw HTML would be confusing for most of our issue creators (think why things like UBB Code were created - other than security) - mind you, its better than only entering in plain text!