Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Issue Description field generates Communications Breakdown message for a specific string.

We have a JIRA on-premise server instance at version 8.7.1.

Have encountered a problem where the following string "Currently eDEN allows the MA user to be able to issue a composition variation, this should be restricted to AiB and CMA users only." generates a Communications Breakdown error when entered against the Description field.

If I insert a t before only in the string then it will save correctly.    I've looked in the log and cannot find an error message that would indicate any more info.  It seems like a formatting/special character type issue. Thanks for any suggestions.

1 answer

0 votes
Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 22, 2020

Hi Gregor,

have to tried to copy the string to a plain text editor to probably spot if there is a special character which Jira (and/or the database) is troubling with?

Have you also tried to enable SQL debugging, which might be of help tracking this effect further down?

Just in case (and due to further details - as you said even log files do not record anything suspicious) I'd recommend to double check the database server for possible error messages and to double check it's configuration - in first step probably using "Atlassian Troubleshooting and Support Tools" (
Specifically please kindly check if the database is supported and if the collation is a supported one.
All further steps would depend from findings and it is quite hard to tell right now where to start from.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events