Getting automation errors, doesn't create an issue

[Colleen]

Hello, I have an employee who has been setting up automations, but they've been showing errors. The Host Name, Issue Source, and Terminal Model are fields it says are required, but when those fields are specified in the automation it still gives this error. I want to keep these fields as required, if possible. How can I overcome this issue?

[Gaurav · Accepted solution]

Hello @Colleen 

Welcome to the Atlassian community!!

To overcome this problem, these fields (Host Name, Issue Source, and Terminal Model) will need to be set to a value by the Automation.

Probably you can define some default value and set that, which later can be changed to the exact value.

Please accept the answer if this helps solve your query else respond and allow others to share input.

[Bill Sheboy]

Hi @Colleen -- Welcome to the Atlassian Community!

For automation-related questions, it may help to post images of your rule and the audit log.  That will provide the community context to offer ideas.  Would you please add that to your question?  Thanks!

And...that audit log error may indicate custom fields are either missing from a view, not accessible for the user the rule runs under, or the fields have no values (as Gaurav suggested).

Best regards,
Bill