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,
I've set an automation rule on new issues created on a project (type software managed by team).
The rule works fine if I create a new issue in that very project.
I have a second project (type service management) that creates tasks in the first one.
The aforementioned rule doesn't work in new tasks if those tasks were created from the second project.
I've performed multiple tests and simplified the rule to the maximum and the problem seems to arise only when the task is an "inherited" one (created from the other project).
Could you please suggest anything else to check?
Thanks,
M
Issues are not created "from projects", but in some places, Jira assumes you mean "the last project I was active in" (mostly when you're in a screen that is for a project or issue within a project).
Is your automation global? If it's a project automation, then it's only going to pick up issue creation when the issue is being created in the project the automation belongs to.
Hi, Nic.
Thanks so much for pointing me in the right direction.
As a workaround I finally set up a scheduled check for all new issues created instead of using the "issue created" trigger.
Regards,
M
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.