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

How can I make transition of linked issues when Sprint Started Automation for JIRA?

I have 2 boards:

  • Board DEV
  • Board QA


In Board DEV I have issues that are linked to issues in Team QA.

I want to automate that when starting the Sprint in Team DEV, for all issues that have linked issues to Board QA, I want to move them to the appropriate status in Team QA. Is it possible? I am missing one more level of Branch rule / related issues. Is there a workaround for this?


What I'm trying to do:


But then I get the error:
Can't branch rule as it requires issue(s) in the context for this option. More than likely you have a trigger that doesn't insert issues into the rule chain. e.g. Scheduled rule not running a JQL query. Creating an issue does not put an issue into the context, you have to branch on it directly.


So ok, when I change it to:


I miss one more Branch rule / related issues to somehow highlight that I want to make action for linked issues in just started Sprint.

Any ideas how I can cover this scenario?

1 answer

0 votes

Yeah the only way around this limitation (issue linked at is to set some sort of flag (either a field or a status) on the issue that's on the Board A. Then have a different rule that listens of that trigger, which then loops over the related issues. You'll need to set the flag to enable the rule to be triggered from another rule in the 2nd rule


Rule 1:

  • Trigger on Sprint started
  • Loop over issues in Sprint
  • Transition to: "QA Issues ready" or something

Rule 2: (must have flag to run from other rules on)

  • Trigger on: "QA Issues ready"
  • Loop over related QA issues
  • Transition the QA issues to appropriate status

Thank you so much @Mark Chaimungkalanont !

I have tried it, but with no success, because the rules fire up indeterministically. I didn't know about the existence of this magic "Allow rule trigger" checkbox, which forces to fire the second rule after all the previous ones.
It helped. Case solved. Thank you again!

Suggest an answer

Log in or Sign up to answer
Site Admin

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