Ticket created by automation does not trigger a cascaded rule

Alexander Kolev November 25, 2024

I have the following set up

  • Proj A: an automation rule at some point creates a ticket in Project B
  • Proj B: an automation rule with a trigger on 'Issue Created' creates subtasks on the newly created ticket

If I manually create a ticket in Proj B, everything works like a charm. When I exercise the full flow (i.e. Proj A creates the ticket), the rule in Proj B is not triggered at all and even more strangely - the audit log doesn't show anything relevant as if this is not expected to work in the first place

Is this expected behavior?

2 answers

1 accepted

2 votes
Answer accepted
Arun Unnikrishnan
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.
November 25, 2024

@Alexander Kolev Just check if this option is checked in the sub-task creation automation. 

Screenshot 2024-11-25 184103.png

Alexander Kolev November 25, 2024

That was it! Thank you so much, @Arun Unnikrishnan 

0 votes
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 25, 2024

Hi @Alexander Kolev and welcome to the community,

I believe that you have to setup the scope of automation in project A, to include project B as well. Then run your rule and let me know if that resolved your issue.

Alex

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events