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!


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
Community Members
Community Events
Community Groups

linked issue status check in automation

Gods of Automation and JIRA,

I have the following problem:

Given a four-phase task execution that works perfectly in a given project. Creates subtasks under the main task, when a subtask ends, a phase builds on it, all the way to the end.

However, when I want to create one phase in another project, it is created as a linked issue, but the automaton running in the base project cannot check the status of the linked issue. I tried every option, I looked it all the way, but it doesn't work, I can't move on with automation.

Help solve this by not having to buy any new add-ons, but just using the basic tools.

1 answer

Hi @laszlo.fischbein -- Welcome to the Atlassian Community!

To view/add/alter issues in different projects with automation rules your rule needs to exist as a global or multi-project scope rule.  Depending upon your version and license level this will consume execution counts up to your service limits.

One work-around to do this with a project-scope rule is to instead call the REST API form the rule.  This will significantly slow down the rule, and could also then run up against your execution time limits.

Kind regards,

I tried both as a global and multi-project rule, but it didn’t work at all

Would you please post an image of your global/multi-project rule, including an image of the detail section?  I could just be a settings thing. 


Like laszlo.fischbein likes this

in the meantime it has been resolved

I'm glad to learn it is resolved.  How did you fix it?


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events