Automation not adding custom field value to Sub-task

[Steve Fitzgerald]

Long story short, but I'm trying to make sub-tasks for a specific Request Type reportable on a Jira Service Management Dashboard. I'm not able to create a filter so I'm trying to add the request type value to sub-task itself.

On creation, I can create the subtasks without a problem, however, when I try to add a value to the field "Customer Ticket Type" I get the error:

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Customer Ticket Type (customfield_15160)

I checked the sub-tasks fields and the field value is there. When I use another automation (not on issue creation) the "Customer Ticket Type" field gets updated. I'd prefer to do this in one automation. Any suggestions?

[Francis Batilo · Accepted solution]

@Steve Fitzgerald ,

I'll help you out on your inquiry. 

This usually occurs when the field you're referencing is not available on the screen associated to your issue type. In this scenario, the automation is trying to access the field when it isn't there, thus the error. 

In your edit/view screen, the automation rule worked because that field exists in that screen.

I have a hunch that your create screen and edit/view screen are two different screens, and the field you're trying to use is only available on the edit/view but not on the create screen. 

To fix this, you'll have to add the aforementioned field into the create screen.

Let me know how you go.

Cheers,
Francis

[Steve Fitzgerald]

That worked. Thank you. 

[Ste Wright]

Hi @Steve Fitzgerald 

I'd check out this help page as a starting point: https://confluence.atlassian.com/jirakb/unknown-fields-set-during-create-they-may-be-unavailable-for-the-project-type-error-on-create-issue-or-edit-issue-action-in-automation-rule-1116275263.html

It's possible the field isn't on the "Create Issue" screen for Sub-task - without it, Automation cannot utilise it in the rule. You might even have different Screens for Create/Edit, you can check this out in the Sub-task's Screen Scheme.

Add the field to the Sub-task's create screen, and this should rectify the issue.

Let us know if this helps!

Ste

[Brittany Montgomery]

Hi Stephen, 

I'm having the same issue, except that the two fields I want to set on an automation are already on the Subtask Issue Type level. Is there custom HTML coding that can be added in the text field under more options, additional fields, or a better alternative? The fields are labeled "Compliance Lead" and "State Manager".