Spellchecking is not something I have found to be a function of Jira itself. At least not yet. More often this tends to have become a function of your browser that is loading the Jira page itself.
Depending on what browser you are using will determine what settings are necessary for the browser to be able to do this.
As for Jira, not all fields are the same. Certainly a description field is expected to be spellcheck-able in the browser, but other fields such as labels have an expectation within Jira to always allow for the new creation of a label directly in the issue itself. Hence that field isn't the same as a text/description field and in turn I would not have the same expectations of it.
Have you found certain fields are working for this while others are not? I would be interested to see if we can better understand exactly what type of custom field works here or does not. It might not be something we can configure directly in Jira since in my experience the spell checking is being provided by the browser, not the site, but the more we can learn about this perhaps we can offer some other insights here.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs