Why does copying a user field to Assignee when creating a sub-task in a Rule cause an error?

[Phil Bustin]

*** NOTE: After I entered the screenshots below, I added a branch to set the sub-task Assignee.  However, 1) The log entry shows the Assignee as blank.

Here is the Rule component:

Here is the error:

[Bill Sheboy]

Hi @Phil Bustin 

I numbered my questions to try to help...

(1) What is the purpose of the first Re-fetch Issue action in your rule?  Is that needed due to some workflow transition stuff happening (outside the scope of the rule)?

(2) What type of project is this: company-managed or team-managed?

The create issue action you show is copying the value of the Production Control Admin field to the Assignee...

• (3) Is the Production Control Admin a single select or multiple select user field?
• (4) Have you checked if there are multiple fields named Assignee?

(5) After the rule runs, did you check if the assignment of the sub-task actually worked and the log error is wrong?

(6) Finally, I wonder: this rule is using the Create Issue (rather than the Create sub-tasks) action so you can use a specific sub-task issue type.  As sub-tasks are parts of their parent issue I wonder if assignment is a two step process for sub-tasks, requiring first to create the specialized sub-task and then assigning in a separate step.  Perhaps try that.

Kind regards,
Bill

[Phil Bustin]

When the copy to Assignee was included in the create sub-task component, it didn't work. 

To work around this, I created a branch after the create sub-task component; in the branch, the copy works.

[Rebekka Heilmann (viadee)]

Hi @Phil Bustin 

The error says that the Sub-Task's Field Configuration in the project doesn't contain the field Assignee i.e. the field is hidden. Have you checked that?

Manage issue field configurations | Atlassian Support

[Phil Bustin]

I don't believe the field is Hidden.  Would Hidden mean the field is not on the view screen for the project?  I don't think that is the case.

[Rebekka Heilmann (viadee)]

Yes and no. The field could be on the Screen but hidden per Field Configuration. It would may or may not be hidden when you view the issue as Edit and View Operations are different.