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!


Cross Project Status Change


Thank you for your time.

I am trying to acheive below automation.

Project A has status Open,In progres, In Review ,Done

Project B has status Backlog, Selected for development,In Code Review, Accepted.


My requirement is to change status of project B depending on transitioning of Project A issues.

For Eg If issues of Project A is transiitoned to Open or In progress  then issues of project B should transition to Selected for development.



2 answers

2 accepted

0 votes
Answer accepted
Curt Holley
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 15, 2023

Hi @Vivek Karna 
Welcome to the community 😊

As @Kristopher Perez has alluded to with his rule. Linking the issues is key.

You may well have known that and are doing that. But as you never mentioned the conditions under which a Project A would move a Project B issue, I thought I''d point it out.

0 votes
Answer accepted
Kristopher Perez
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.
Mar 13, 2023

To get started, I would create a separate Automation for each Transition.  This will keep the transition light weight and easy to debug.

It would look something like this:

  • Tigger = Issue Transition (scope it accordingly, do you only want it to transition from one status to another, or do you not care about the source transition, think about it)
  • Branch Rule = Released Issues with the specified Link Type
  • Action = Transition to the Target Transition

Depending on how smart you want to make it, you will have to play around with additional conditions.


Screenshot 2023-03-13 at 2.22.31 PM.png

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events