My problem automation is not working

[RAMCEL MAGNAYE]

Please help me investigate my automation i dont know how to fix this error 

[Trudy Claspill · Accepted solution]

Hello @RAMCEL MAGNAYE 

The error message in the Automation rule log is indicating that the Problem Trigger field does not have a value but is a required field.

Looking at the images you provided, the value that you have specified for that field in the Create Issue action:

...doesn't match the values that are actually available for the field in the Create Issue dialog.

Notice in the Create Issue dialog the value has parentheses and in your rule it does not.

That suggest there may be more than one field named "Problem Trigger" in your instance with slightly different options, and in your rule you have chosen one that is not the one actually used in the issue type you are trying to create.

In the Automation Rule when you used the "Choose fields" pull down to select that field, did you see more than one field with that name?

Are you working with issues in Team Managed projects or Company Managed projects?

You may need to used Advanced Editing with JSON in the Create Issue action to edit the field, using its custom field ID to identify it instead of its name.

You can find information on how to edit/set a field in that manner in this document.

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

And you can find information about how to determine the custom field ID in this document:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

If you have more questions about that, please let us know.

[RAMCEL MAGNAYE]

thanks @Trudy Claspill will check this if the issue presist i will let you know thanks 

[Fernando Eugênio da Silva · Accepted solution]

@RAMCEL MAGNAYE ,

Well, it seems correct. But just try to check if the field Problem Trigger is already added in the Create issue screen for the Issue Type selected.

We can see you're sending a value for the field, but maybe automation is not filling him because the field is not added in the Create Issue Screen.

If this is already checked, I would say to verify if the field 'Problem Trigger' is looking for a specific value and for this cause automation is showing an error.

[RAMCEL MAGNAYE]

Hi @Fernando Eugênio da Silva  yes it is added on the screen , so the field "Problem Trigger" cause the problem ? 

[RAMCEL MAGNAYE]

Hi @Fernando Eugênio da Silva  yes it is added on the screen , so the field "Problem Trigger" cause the problem ?