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,457,745
Community Members
 
Community Events
176
Community Groups

cloned issue as a trigger in automation for jira

Project A; if a user story has a specifiek status I would like to clone the item to project B

So far no problem but when the item is cloned to project B it should automatically create a set of sub-tasks. I thought I could do this with automation using "issue created" as the trigger but it seems that the rule is not triggered because the issue in cloned to the project.

what can I use as a trigger to automatically create the subtasks?

2 answers

1 accepted

5 votes
Answer accepted

Hi @Ariane Voorbeijtel Cannenburg ,

Maybe it is because your second rule needs to check this in order to be able to be triggered by another rule:

trigger.png

Is that the case?

Hope it helps.

Regards

Yes!! that is the solution. Great thanks!!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events