Error creating issue: Reporter is required. (reporter)

[Steven Kent]

Hi

I have an automation in Jira that is triggered when an Epic is created where the Component field is not empty. It then creates a Task and a number of Subtasks within the Epic, assigning the Epic Reporter as the Reporter for each, and assigning the Assignee to one of the subtasks.

I've had this working as a test case for a number of weeks.

Today I went to change the rule details to swap "Component field is not empty" to "Label = auto_comms". However now when I create the Epic, JIRA says the automation fails as "Error creating issue: Reporter is required. (reporter)".

The issue always has a reporter when created, and this has worked in the past, so I don't understand why it's failing now.

If I remove the steps in the automation that assign the Reporter to Task and Subtasks, the automation works fine, adding Automation for Jira as the Reporter. I can live with this but want to understand why the previously working automation, now is not.

[Alex Koxaras _Relational_]

Hi @Steven Kent 

It would be great if you could post a screenshot of your rule.

[Steven Kent]

Thanks @Alex Koxaras _Relational_ have added below

[gyorgy_rauf]

@Steven Kent you might need to check the create screen of the issue type you are trying to create. If the reporter field is not on the create screen it can't be set, however since the field is always mandatory it is automatically set to the user who is actor of the automation rule.
https://support.atlassian.com/automation/kb/error-unknown-fields-set-during-create-they-may-be-unavailable-for-the-projecttype/

I ma facing the same issue at the moment, this was working fine on data center even if the reporter was not present on the create screen but in cloud it's different.

If this is the solution, then we are going to face another issue where for manually created tickets users can set the reporter which might be misleading.

[Steven Kent]

Thanks @gyorgy_rauf  but my create issue screen does indeed include Reporter, automatically set to the user who is creating the issue (i.e. whoever clicked the Create button)