Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,467,204
Community Members
 
Community Events
177
Community Groups

How to use automation to create sub-tasks for a new issue and assign those subtaks to an assignee?

Edited

Updated Per Bill.

 

Hi forum!

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:

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Assignee (assignee)
The Assignee field is in the field configuration for the Sub-task issue. 
Thanks for any help.
-Curt
Rule:
image.png
Detail of Create Rule (Note Assignment):image.png
Error Received in Audit Log: image.png
Result:
image.png

1 answer

0 votes

Hi @cpasfield 

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:

  1. After seeing that error, did the rule still assign the user to the sub-tasks successfully?
  2. Is this a project-scope or global/multi-project scope rule?
  3. Is the target project for this rule company-managed or team-managed?

Best regards,
Bill

Hi Bill,

 

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!

 

-Curt

Simmo Atlassian Team Aug 22, 2021

Hi @cpasfield

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.

Cheers,

Simeon.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events