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

Use Keywords to automatically change comment visibility of Service Desk comments

Hello there,


im starting to get used to scripting with behaviours. At the moment i have following problem:

I have 2 jira projects, 1 is a service desk project. im using a sync to keep both projects up to date. The only problem i have is that whenever a new comment is added, it gets synced an internal comment into my service desk project.

Now i thought of maybe using a keyword to decide which comment stays internal and which comment is public. 


So i thought of something like:


if(new comment is added to service desk issue) {

if(!comment contains keyword) set comment to public

i would be thankful for any help or if someone knows a workaround, that would be great aswell!


thank you very miuch


1 answer

0 votes
Alejandro Suárez
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 Leaders.
Feb 21, 2020 • edited

You could add a recursive transition (from all statuses to all statuses) and with the behaviour plugin or custom validator force the commentary to be set. You could name this transition "Public Commentary" and that's it, all commentaries coming from this transition could be synced to the another project marking them as public.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events