Can I render an issue number in JIRA comments as Strong?

[timrmoore]

We've just upgraded JIRA and imported all the data. In the comments, where an issue number was breviously rendered as strong (*strong*) it's no longer rendering (shows as *JRA-123* instead of JRA-123) Is there a way to render text that includes an issue number?

[timrmoore]

I'm guessing the answer is No, you can not render text as strong if that text contains an issue key.

It would be good to get some clarification from Atlassian though - please. Does this relate to all text rendering?

[Jobin Kuruvilla [Adaptavist]]

Can you check if the comment is now using Wiki Style Renderer or not? You can find it in the field configurations.

http://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour#SpecifyingFieldBehaviour-ChangingaField%27sRenderer

[timrmoore]

Hi, yes thwe field is using Wiki renderer. I have edited the existing comment with strong markup and that works OK. I've also edited the issue key by removing the hyphen and that works too.

The piece of text that they had previously made strong was actually a file name (e.g. JRA-123_analysis.xls). It seems that the issue key is being recognised and that's what is preventing the text from rendering as requested.

[JamieA]

If you're talking about the rendering of bold text in asterisks then you should the renderer for Comments in your field configuration, sounds like you want the wiki markup renderer.

However, I'm not sure why this should have been undone during an upgrade.

But if you're talking about issue keys these should be found and linked automatically, assuming JRA-123 lives in the same jira instance.