Will required fields prevent sub tasks from being created?

[Peggy Burns]

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

[Nic Brough -Adaptavist- · Accepted solution]

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.

[Tessa Tuteleers · Accepted solution]

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

[Peggy Burns]

These are custom fields that I created.   Are you both stating that I need to create a field configuration and add these fields to the subtasks?  Do I have to add them to the subtasks?  I really only want these newly created custom fields on the Bug.  I have a separate automation to bring the Description field forward to the subtasks.  This is the only field I wanted to see under subtasks.  Is it possible to have the subtasks ignore the custom fields and just create the tasks?

[Nic Brough -Adaptavist-]

>Are you both stating that I need to create a field configuration and add these fields to the subtasks?

No.

Field configurations do not add fields to issues.  They are a handful of flags or settings for the fields.

Your project is using one field configuration, and you've said "field X is mandatory" in it.  If you create a new field configuration and tell Jira to use that for sub-tasks, you can make the fields optional.  Which will then allow your automation to work.