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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,459,285
Community Members
 
Community Events
176
Community Groups

How to copy comment from ServiceDesk to "normal" project?

In our setup we plan to have 1 Jira ServiceManagement (JSM) project as single point of entry for all our customers.

Once a ticket is created automation should create a new ticket in the appropriate Jira project dedicated to a specific team. This ticket should be linked to the original (JSM) ticket. So far, so good. This works.

But now we want a comment which is entered on the JSM ticket to be copied to all linked Jira tickets (in the projects).

Currently I have the following automation, but this is not doing anything?

Comment_automation.png

 

And of course we also would like this the other way around, but no luck on that route also. Any help is highly appreciated

1 answer

1 accepted

1 vote
Answer accepted

Hi,

Can you please share the log?

I create the same automation, a little different (see my picture,) and this is working fine because the rule has to be restricted to all project where you have linked the issue.

Capture.JPG

Br. Mario

@Jeroen Gouma As Mario mentioned, it might be because your rule is scoped to only the project that it is being triggered from.

To check this, you will need to go to Admin cog > System > Global automation and click into the rule. In Rule Details, if it says Single project, you will need to change this to Multiple projects and select the two projects that are being used by this rule.

The only cross-project action you can use with a rule scoped to a single project (the triggering project) is Issue Created.

Hope this helps!

Like # people like this

Mario, Callum,

thanks for your help. Changing the scope to both projects did the trick. It's working like a charm now.

 

Learning more and more...

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events