Subtasks NOT Inheriting Request Type Custom Field value from Parent

[Kay Kalunga Kabwe]

I have a custom field called 'Request Type' on my Jira Cloud instance whose value doesn't get replicated in the subtasks ( we have a ton of them). As a result, when categorizing by Request Type, over 50% of tickets don't have a Request Type greatly impacting accurate reporting. I've tried setting up an automation rule via the "Edit Issue Fields" action as advised in the community. However, am getting this error.

When I go to the advised "Edit Request Type", I don't get the option to copy the value from the Parent/trigger issue and I have to choose a specific type?? I just need the subtask to assume the same value as the issue that created it (ie. Parent).

[Robert Wen_ReleaseTEAM_]

Hello @Kay Kalunga Kabwe ! Welcome to the Atlassian Community!

I think the name of your custom field is the same name as the system-defined custom field Request Type and this is confusing your automation.  You may be selecting the system field instead of your custom field.

As a test, rename your custom field and see if you can get your automation to work.

[Kay Kalunga Kabwe]

Hi @Robert Wen_ReleaseTEAM_ Unfortunately, I can't edit or modify this Request Type

[Robert Wen_ReleaseTEAM_]

That's the system field Request Type.  That's why you can't edit or modify it.

Did you create a custom field or are you using the Request Type provided by the system?  If you are, it's only meant to associate with a parent type, not a subtask type.

[Kay Kalunga Kabwe]

If its only meant to associate with Parent type, why do all subtasks have it? Albeit unpopulated? And yes, it does seem to be a system field but its appearing on Custom Fields in my settings as shown here. 

[Robert Wen_ReleaseTEAM_]

Interesting.  Normally the Request Type field isn't on the default subtask screen.

Anyway, here's more information.

https://support.atlassian.com/jira-service-management-cloud/docs/whats-the-difference-between-request-types-and-issue-types/