Automation breaks because of a required field that is not even used in subtask screen

[Celina Kim]

Hello, 

I set up an automation to create a subtask when any new issue is created. But, it keeps showing an error that one of a required field makes it fail. It's our "Tag" field. So, I took out "Tag" field from subtask screen. But, the automation still fails. How can I resolve this problem?

I'm attaching the automation setting just in case. 

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Community!

Screens do not have anything to say about fields being mandatory.  You have two routes to make this work - either make the field optional in the field configuration (not the screen), or have the automation set your "tag" field.

[Celina Kim]

Thanks for your response. I fixed the error!

[Amit Jadhav]

Hi Kim,

Can you please share the step, how you fix this?

[Pragnesh Patel]

Amit - When you automate to create sub-task, click "Add Field" and select "Tag" Field and give value or  alternate option is given by clicking the "..." next to field and select "Copy from Issue"

Hope this explains!

[Maroof Ahmed Malik]

I also have the same issue. But im not using Tags in my screen. how can i solve it otherwise?

[Pragnesh Patel]

Maroof, "Tag" is the custom field name in the above example. When you create sub-task with automation, you need to make sure the required field has some value. In above example, I have explained to copy the value of "Tag" field from parent issue into sub-task. That will solve the issue as the required field has value what parent issue has.

Hope this helps to clear your problem.

[Pragnesh Patel]

Here you can replace "Tag" field with your field...