The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Gregor Dow
August 10, 2020

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 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?

https://confluence.atlassian.com/jirakb/enable-sql-query-logging-in-jira-server-665224933.html

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" (https://confluence.atlassian.com/support/support-tools-plugin-790796813.html).
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.

Cheers,
Daniel