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

Trying to use Project Automation to Trigger Legacy Automation Rules

I'm having an issue converting an old JSD (Legacy) Automation which is using a "Customer Notification" template when sending e-mails.  This template has elaborate formatting (HTML I believe).  Because of this I decided to keep the "Send e-mail" portion of the Legacy Automation and transfer the other sections to the Project Automation (Automation for Jira).

My issue is that I'm having a problem trying to trigger the Legacy Automation.  Here's an example that is not responding:

  • My Project Automation calls a SIL Script which adds Request Participants to my Jira issue.
  • I had set the JSD Automation trigger to "Participant added".
  • The JSD Automation does not trigger.

Anyone have any ideas on how my new Project Automation can trigger an existing JSD Legacy Automation.



2 answers

Hi @Vincenzo Ciaravella 

I know this isn't the direct question - but would it not be easier to move the other rule to Project Automation, even if it has complex formatting?

Automation will work fine when the two rules are no longer in Legacy - and the effort to make the Legacy rule work could be spent moving the rule across.

You might not find many answers here otherwise, as many users (including myself) don't use Legacy Automation anymore.


0 votes

Hi @Vincenzo Ciaravella ,

I agree with the answer by @Stephen Wright _Elabor8_.

Maybe the JSD Automation does not trigger because the action of adding a participant is executed through the REST API (by an automation rule) rather than manually.

Please note even the new Automation rules need to enable a checkbox on the Rule Details section to allow a rule being triggered by actions made by another automation rule:


Anyways, I'd also substitute the legacy rule with a new one.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events