How to fix broken create issue automation rule?

[Danno]

I've tried to create an issue in a different project using automation and it fails for the following errors. The Date needed field gets filled out when the new issue creation window opens. See the picture below the audit screen.

Here is the flow I created.

[Marco Brundel]

Hi @Danno ,
When creating an issue in the PR project it is therefore required that the "Date Needed" field is filled.
Where is this field set up required, do you know that? (That this field is required can be, for example, a validator on the create transition in the workflow of project PR.)

Is it an option to also fill the field via the rule?

Regards, Marco

[Danno]

Good Day Marco,

Yes, the Date Needed field is currently a required field (it is set as required in the field settings) in the Purchase Req. project and I do enter a date when it comes up in the create issue screen as you can see in the above screen shots. I do find it interesting that the screenshot I have doesn't have the red asterisk that indicates Date Needed is a required field like on the Summary Field The only validator in the Create transition is the system one of "Only users with Create Issues permission can execute this transition."

I do not have anything in the automation rule to set a date for that field. I also do not know what the second warning message means except that it might be indicating that the rule has already failed on the Date Needed step and so it ignores the create linked issu part of the rule which seems to be what is happening.

[Marco Brundel]

Hi,
You want to create an issue in project PR via the automation rule. But because the field "Date Needed" is mandatory when creating an issue in project PR, the issue is not created and that is what the first error says.

And I think that also gives you the 2nd error, that there is no issue to link.

regards, Marco

[Danno]

Marco,

I hve been able to solve the first problem of my rule. It turns out you need to have the automation rule set the required field. This allows for the issue to be created which then allows for the issue to be linked back to the triggering issue. Now I have to solve how to get the rule to correctly assign the issue to the same assignee in the trigger issue and get an automation rule in the the project where the new issue has been created to set a custom field after it has been created.

[Marco Brundel]

@Danno 

If you choose the Assignee field at the Create Issue, you can choose "Copy for trigger issue". Is that the solution for the Assignee field for you? Regards, Marco