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,456,776
Community Members
 
Community Events
176
Community Groups

Automation Rule for cloned tasks in two different projects

Hello Community,

I want to define the following automation rule for two different projects (Project A and Project B) with the following steps:

1) If in project A a label of a task is changed to "customer" the task shall be cloned in Project be with the same status.

2) The cloned task in project A shall be automatically related to the cloned task in Project B if label of task in project A is set to "customer"

3) If the cloned task  with the label "customer" in project B which is related to the task in project A gets a different status, lets say "finished" the related task in project A should move along the Kanban board to the same status.

 

So far I have the following rule, it covers the first 2 steps need some other conditions for the 3 step:

Jira Rule.PNGMove Task.PNG

Thank you for the support!

1 answer

0 votes
John Funk Community Leader May 30, 2020

Hi @vlad  - Welcome to the Atlassian Community!

You will need a second rule to handle number 3. 

You should use a rule based on a Transition change. 

Could you explain it in more detail or maybe with a screenshot? So if the task status in Project B changes the same status change has to happen for the task in Project A. The status of the task in project A depends on the status of the related task in project B. For example if task in project B has status finished the task in A should have also the same status and move to finished in the kanban.

John Funk Community Leader Jun 01, 2020

Your first rule above is based on the change in a value of a field (not a status).

Your second rule needs to be based on the the task in Project A transitioning to a certain status. Then that causes the issue in Project B to transition to the same status. 

You need need a third rule for when B transitions to a status and you want A to transition to the same status. 

Suggest an answer

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

Atlassian Community Events