Text not to be converted to Jira issue link

[pauli_innamaa]

How can we prevent text string being treated and shown as a Jira issue link? 

We have the set-up where our document naming convention is close to the Jira issue naming convention. This causes situations where we refer to a document, say, ABC-1234 in Jira Issue. When this field is rendered in Confluence table, the text is shown as a hyperlink ABC-1234 although it should not be a hyperlink, instead it should be plain text. Is there an escape character or some other way to prevent Confluence treating those strings as links to Jira issue.

[Pavel Junek · Accepted solution]

Hi @pauli_innamaa,

It is strange -  this behaviors, which you describe does not happen on our Confluence. It only changes to a Jira link if I write a comment in Jira, in Confluence an abbreviation such as ABC-123 is displayed as plain text. When I copy whole Jira URL link and paste him to Confluence page, them automatically transform to link:

Please do you have a proven procedure when the problem you describe happens to you?

Thank you

Pavel

[pauli_innamaa]

Hi Pavel, 

thank you for interest and quick reply.

Please see in the screenshot a real example of how the problem appears. This masked screenshot is from a Confluence page where a table of project's milestone criteria is generated: Specified columns of Jira issues that fulfill certain conditions are shown (Jira issue fields Key, Summary, Stream, Status and Justification). In the example you can see that the Jira issue's Key is TA032-5. In the Justification, we are referring to a document whose Document ID is TA032-006. This is not a Jira issue - it is a Document, but Confluence "thinks" that this refers to Jira issue TA032-006 or TA032-6. Now, if I go and see the text in Jira issue's TA032-5 field Justification, the text there is plain text, no hyperlink to TA032-006 exists there. So somehow Confluence "thinks" that TA032-006 is a link, but Jira does not. 

I hope I was able to describe the problem clearly enough.

[Pavel Junek]

Hi @pauli_innamaa,

Thank you for more detail information from your side. I can confirm that I have also replicated this issue on my instance.

However, I'm afraid there's probably no way to change the Confluence settings - I think it's a property of the Jira Issue macro :-/

Pavel

[pauli_innamaa]

Hello,

thank you for putting your time and expertise on this. It seems that we just have to cope with that unwanted Confluence behaviour.

- Pauli

[Dan Breyen]

In my Cloud instance with Jira/JSM/Confluence I'm not replicating that behavior.  Any chance you could provide a text example of what you are entering in your table and exact steps to reproduce it?