Why does my automation get an error trying to edit the Assignee when creating a sub-task?

[Phil Bustin]

Hopefully, there's an important clue about the Unknown fields error: In this automation, in sub-task create actions for a different workflow that occur after the one that produces the error, no such error occurs.  Here are the relevant screen shots:

Set Assignee that produces the Unknown fields error in an action to create a sub-task

---

Unknown fields error

---

Assignee field is present but not populated, in the target sub-task issue view screen

---

Assignee field is present in the trigger issue view screen

Successful Set of Assignee field in action in create a sub-task in a different workflow

[Dexter de Vera · Accepted solution]

Check the screen scheme of your subtask. Make sure the Assignee field is included in create screen.

[Phil Bustin]

[removed this reply]

[Phil Bustin]

Thank you Dexter.  When we looked again with a fresh set of eyes as it were, the wrong screen was the Default screen.

[Mohamed Benziane · Accepted solution]

Hi,

check if when you create the issue in the UI, you have the assignee field in your screen. The field need to be in the create screen for this issue type

[Phil Bustin]

Thank you Mohamed.  When we looked again with a fresh set of eyes as it were, the wrong screen was the Default screen.