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

How can I escape special characters when sending issues comment through a webhook?


Hi There,

I have a rule that comments issues on a cloud instance with the last comment body of the issues of another cloud instance, by sending {{issue.comments.last.body}} through a webhook:

Comment Body 1.png


I'm having some issues with special characters, e.g.:

Comment Body 2.png

Comment Body 3.png

On the receiving instance I'm getting the following:

Comment Body 4.png

Any suggestion on how to handle this kind of comments?

Thanks in advance!

2 answers

1 accepted

1 vote
Answer accepted

Hi @Pablo Serra 

Have you tried any of the smart value encoding functions provided by automation before sending the message: 

Kind regards,

Hi Bill, thanks for your reply.

I've contacted support and after a little back and forth, they provided me the following function that did the trick: asJsonString()

In my post:

"commentAuthor": "{{ }}",
"commentBody": {{ issue.comments.last.body.asJsonString() }},
"keyBancar":"{{ issue.key }}",
"summary":"{{ issue.fields.summary }}",
"keyIssues":"{{ issue.fields.customfield_10716 }}"

Please note that it must be sent without the quotation marks around the curly brackets.

More info about this function:

Like # people like this

Apparently the problem are the line breaks. Only comments with line breaks failed to impact on the receiving instance.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events