The main problem for me is that, documentation is intentional and often the CASING and SPELLING are too.

Spell check is great BUT auto-correct isn't very good in this scenario. Everyone here has different requirements for the word "Jira" for the purposes of communication. This particular word often need emphasis wiki doco or conciseness in technical doco.

Ideally, the spelling of "Jira" would never be auto-corrected.

To Clarify on Jenny's point. This autocorrect rule is for Server customers.
I just checked in a couple of Cloud instances and the autocorrect in Chrome worked as follows:
JIRA -> Jira
jira -> Jira
jiRA -> jiRA - and other variants are unchanged.

Ok, maybe it isn't the Confluence autocorrect, maybe it's the Chrome autocorrect. I tried editing a Confluence page in Safari, and "Jira" didn't change to "JIRA".

Hi Jenny, despite what you're saying, it looks like Confluence is NOT autocorrecting to "Jira". I'm on Confluence Cloud, and when I type "jira" or "Jira", it autocorrects to "JIRA". So I agree with the other comments since January. 

As of 6.7, the only autocorrect rules we have in place for Confluence Server are:

• jira -> Jira

This is to remain consistent with our branding. The bug was resolved as 'won't fix' as although we no longer autocorrect to 'JIRA', we instead correct to 'Jira', which to my understanding does not resolve the root issue.

Agreed, I'm guessing this is an accidental closure, since this makes Confluence not comply with Atlassian's own branding as launched this past July. (@jmillman)

Finally an answer from Atlassian, thank you @Jenny. But you did not explain WHY you won't fix this bug. For the record, it's not about "jira" correcting to "Jira" but incorrectly changing it to "JIRA".

Why won't you solve that?

Hi all,

I'm afraid we have no plans to implement this in the future.

With the upgraded look and feel for Confluence in 6.7, we have removed some of the autocorrect settings. However jira still corrects to Jira.

To find out more about Confluence's new look, check out our release notes.

Thanks

Jenny Millman | Product Manager, Confluence Server

I see this problem in both Jira Server 7.4.4 and Confluence 6.4.2 - with some deviations as I can enter 'Jira' here without it getting uppercased and the same goes for my Jira DEV and TEST instances !?!?

I cannot find out why my Jira production instance 7.4.4 do this uppercase translationan and why my DEV 7.5.3 / TEST 7.4.4 do not !?

Anyone found a related issue for Jira ?

Hi Team,

   Any fix, we are facing issue with the auto formating with so may words.

I am using the latest confluence version available.

Thanks