Please stop changing my text to a hyperlink!

[wilhelm.fp]

Please stop changing my text to a hyperlink.

An FQDN is NOT a hyperlink. There will never be a case where I will ever want to have you automatically create a hyperlink if I don't use http:// or https:// .
When I refer to one of my company's many domains I do not want you reformatting it as a clickable hyperlink.

myComputerName.domain.com is not intended to be a hyperlink.

http://google.com is intended to be a hyperlink

It makes my text unreadable! Please, how do I stop this from happening?

[Jon Wilson]

I came here because we've had instances of Jira "helpfully" converting a given pair of English words where the user didn't include a space after the full stop into a clickable link which happens to be a link to a malware site.

An FQDN is a DN: it's a domain name. All names in URLs are domain names, but not all domain names should ever be interpreted as valid HTTP[S] URLs. More than that, not every "something.something" is a domain name.

Imagine trying to write a Bug that says "remove references to this site because it's a security risk" and having Atlassian silently making it clickable!

[Nic Brough -Adaptavist-]

A FQDN is the basis of a hyperlink, and is exactly what they are for.  A FQDN should always give you a hyperlink, or at least the most important part of one.

Most humans don't care about the technicalities of this, we just tend to expect something that looks like a link to actually be a link.

I'm not sure how making bits of text a slightly different colour, or underlined, makes your text unreadable.  I am a (poor) speed-reader.  Bad spelling, switching foreground/background colours partway through a sentence, dreadful fonts like "comic sans" or even just SHOUTING, and broken capitalisation or punctuation make things incredibly really hard to read.  But links and FQDNs being consistently shown as click-able is actually easier to read - the colour makes my brain go "useful link, but I don't need to absorb the actual words in there"

[wilhelm.fp]

No, you are wrong.
when I am explaining that the work needs to be in "mycompany.com" why on earth would you make that into a hyperlink? Where do you expect the reader to go if they click the link?

If I type "https://mycompany.com" then I expect that to be a clickable hyperlink.

[Nic Brough -Adaptavist-]

Um.  No.

It's a link, possibly a useful one.  Why not present it as such?  You're not writing usefully if you put in a link when it isn't one.

[Ryan Dasso]

Um. Yes. FQDN's are entirely different than URLs. If an FQDN was a URL, we would call it a URL, not an FQDN. 

Since you don't have any problem with things incorrectly fixing your content, I'll take it upon myself to fix your statement. 

"It's a link, definitely a useful one in all possible cases."

[Nic Brough -Adaptavist-]

Yes, they are, a FQDN is not the same thing as a URL.  But they always have at least one, and it's useful to represent them with a URL.

I am glad you agree that it is a link, a useful one, as I said.

[Finn Hoile]

A somewhat old topic, but I have to agree that JIRA is fairly annoying in how aggressively it updates things as being hyperlinks.

In my JIRA projects, I have to commonly document loose files I have created or modified.  JIRA loves finding anything with a weird file extension and converting it to a broken hyperlink that goes nowhere.

I often have to list out:

- myProcessOne.pro

- myProcessTwo.pro

And JIRA will reformat them and create broken hyperlinks on every single file I list.  I can remove the links easily enough, but it's definitely painful, annoying and fairly illogical in my opinion that JIRA creates them in the first place.