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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Site Admin
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

4,567 views 12 8
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you