Will required fields prevent sub tasks from being created?

Question

Currently I have my "Bug" configured with added automations of creating sub tasks.  I've recently added more fields to the bug, however, they are also required fields.  My sub tasks are erroring on those fields and it's preventing the sub tasks from being created.  How can I get keep my fields and have my sub task automation work?

Thank you,
Peggy

Tessa Tuteleers · Accepted Answer

Hi Peggy,

I'm assuming you're working in a Company-managed project. I read you want new fields for your bug, and they need to be required, but you don't want these fields for the linked sub-tasks?
How are you making these new fields required for your bug?

If you are using the field configuration to make these fields required, you just need to create a new field configuration, where those fields are not required, and add it to the field configuration scheme for your subtasks.

Hope this helps!

* Tessa

Nic Brough -Adaptavist- · Accepted Answer

Fields being mandatory is done at an issue type level, but the default is to simply have one setup for the project, so all the issue types behave the same way.

What you need to do is fiddle with the "field configurations".  At the moment, your project is probably just using one of them for all issue types.

Go to the project admin and find the "field configuration scheme".  This tells the project which "field configuration" to use for each issue type.  You're going to want to create a new field configuration and associate it with all the sub-task types in here (I usually copy the existing one to a new name)

As you've already set some fields mandatory, I suspect you already know what to do with a field configuration, so I won't bore you with that.