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
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
Updated Per Bill.
I apologize if something like this has been asked before but I haven't had any lunch searching for it.
I am trying to create the following automation. When a ticket comes in to create a new onboarding request for a new employee. I would like to automatically create several tasks and subtasks and assign them HR personnel. However, when I add the Assignee field to the subtask in the And: Create New Sub-task step in my automation I get the following error in the Audit log:
Would you post an image of your rule? That may provide some context for the community to offer ideas. Thanks!
And a few follow-up questions:
Thanks for your reply. I uploaded the results of one of my test runs that did not work. My colleague had the same results as I. I just tried it again and it appears to have worked. I didn't do anything other then review the field configurations again...making no changes mind you. In fact all of our test rules that we created to try and troubleshoot what we were seeing, none of which worked before, are all now working.
I appreciate your reply and attention!
I have a look at the logs for one of the executions of your rule above. When we ask Jira which fields we're allowed to edit/set, the assignee field isn't one of those. This is usually related to some sort of screen configuration. You might have a different screen for sub tasks that doesn't have the assignee on it.
I also noticed that you've changed the actor away from Automation for Jira. Is there a reason for this? I ask because the Automation for Jira user is allowed to do a few things that normal users aren't. One of which is to bypass those field configurations. This means that it can sometimes set a field even if it isn't on the particular screen.