Fisheye changesets and revision numbers are not being rendered JIRA comments when JIRA OnDemand is not linked with Fisheye Standalone.

Customers migrating from Fisheye OnDemand to Fisheye Standalone are losing the functionality of referencing Fisheye changesets in JIRA comments. Those changesets references (such as r1234) are not being rendered as links to the actual changeset in Fisheye.

This works when JIRA OnDemand is integrated with Fisheye OnDemand, but it's lost after Fisheye is migrated to it's standalone counterpart and linked with JIRA OnDemand.

Any text that has the revision number format r1234 will not be rendered in JIRA, even if the instance never had Fisheye to begin with. Any string of this format will be invisible.

This lack of functionality is not being informed to customers in any of the migration documents.

JIRA Standalone users can use the Application Links Link Rendering Plugin to achieve this functionality, but this plugin is not available in OnDemand.

Workaround

Users can still use monospace formatting and the text displayed as r211144

To achieve this please enter the revision as:

{{r211144}}

As a clarification, this only affects words that match exactly:

r[0-9]+

For example, myr211144 or rev211144 will render correctly.