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.
Jira Cloud. Multiple project service desks. Relatively new to the automation section. I'm trying to figure out an automation rule that will set the the Assignee to unassigned when an issues is moved from one service desk project to another. Is this a field that can be modified with custom automation rules?
Hi Geoffrey,
Welcome to Atlassian Community!
It’s possible to set an assignee to unassigned when moving an issue using an add-on, since on Service Desk built-in automation there is no trigger for that.
You can use the add-on Automation for Jira (if you move less than 300 issues a month, you can use the free version).
Regards,
Angélica
Unfortunately, an add-on is not going to be an option for me. Is there a way through Jira automation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jira automation does not have a trigger to run when an issue is moved, that's why it would be necessary to use an add-on, otherwise, the best option would be manually set the issue as unassigned before moving.
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.