You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all,
I need some thoughts here. Is there a way I could implement a rule which creates an issue in current project (to which I belong) due to trigger from a story created in another project (guess I do not have access). I have created a rule for the other way around (from my project, issue created in destination, but this is the other way around).
Hi @JunoB
The only two ways to do that: the way you did (rule in source-triggering project) or a global/multi-project scope rule.
There are limits to the number of global/multi-project scope rule executions per month, depending on your license level. Please look here for more information: https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/
Kind regards,
Bill
Hi Juno,
Yes, you should be able to do that. Just use Automation for Jira as the Actor. Or another ID that has access to the other project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.