Issue Summary

Some customers are using message custom filed  introduced from JIRA Toolkit Plugin. However, if the default value of message custom filed contains bracket character, after adding comment, the comment editor will turn into invalid status instead of closing comment editor normally.

See detail in Steps to Reproduce section.
Except the above UI problem. A syntax error is noticed in console of development tool.

The above problem happened in Chrome. Also, according to customer, the below problem may be happened to Firefox

• Duplicated comments may be added.
• The third filed tab may disappear.

Steps to Reproduce

1. Install JIRA Toolkit Plugin
2. Create a custom filed of Message Custom Filed(for edit)
3. Associate the above custom filed to a screen
4. Edit the default value of above custom field to a value with bracket, for example, (abc)
5. Edit the screen , add a new tab(second), and put the custom field to the second tab(If the problem is not reproduced, add the third tab, and put the custom field into the third tab )
6. Create a ticket
7. Input some comment and click the Add button

Expected Results

Input editor area will disappear and comment will be added to comment list(history) normally.

Actual Results

Input editor area persist showing in an invalid status as below, though comment has been added to comment list.

The above problem happened in chrome.

According to customer, for firefox, duplicated comments may be added, or the filed tab may disappear.

Workaround

• remove bracket from default value of  Message Custom Filed.
• diable Jira Toolkit Plugin in Manage apps.