nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Celina Kim_el05hi

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.

Accepted answers

Nic Brough -Adaptavist-

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.

All comments

Nic Brough -Adaptavist-

Welcome to the Community!

Celina Kim_el05hi

Thanks for your response. I fixed the error!

Amit Jadhav

Hi Kim,

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

Pragnesh Patel_5a80sn

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!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud