Jira Automation Failing to Set Team Field on Issue Creation

[Lukas Maul]

Hello Atlassian Community,

I am experiencing an issue with a Jira automation rule that is failing to set the "Team" field when a new issue is created.

Details:

• Goal: The automation should set the "Team" custom field to "Team IT Support" whenever a new issue is created in our project.

• Trigger: Issue Created

• Action: Set entity property

• Entity Type: Issue

• Property Key: customfield_10001 (This is the correct custom field ID for the "Team" field, as identified in Jira settings)

• Property Value: 4270d2c6-2e41-413c-97e5-9b05623d9ea0 (This is the ID for the "Team IT Support" team, obtained from the team's URL in Jira)

Problem:

The automation rule runs, but the "Team" field is not being set. The audit log shows the following error: "Failed to set entity property for issue: ITS-292" (where ITS-292 is the issue key). I've attached a screenshot of the audit log for your reference.

Troubleshooting steps already taken:

• Verified the custom field ID (customfield_10001) is correct.

• Team ID (4270d2c6-2e41-413c-97e5-9b05623d9ea0) i'm not shure if it is correct.

• Ensured the automation user has the necessary permissions to edit issues and modify the "Team" field.

• Tried setting the property value without brackets.

Questions:

• Why is the automation rule failing to set the entity property?

• Is there a specific format required for the property value (Team ID) that I am missing?

• Is there anything else I can try to resolve this issue?

Environment:

• Jira Cloud

Thank you for your assistance!

[Marc - Devoteam · Accepted solution]

Hi @Lukas Maul 

Welcome to the community.

This can only be done by setting this up via JSON, so via the more option in the edit action.

Code:

{
"fields": {
"customfield_10042:"4270d2c6-2e41-413c-97e5-9b05623d9ea0"
}
} 

[Lukas Maul]

Hello Marc,
thanks for your feedback.

I have used the code, but unfortunately Jira gives me the error message: No valid JSON.

Is there a problem with the syntax?

Here are the screenshots of the code & error

[Marc - Devoteam]

Hi @Lukas Maul 

Sorry typo on my side, a " is missing from the code.

{
"fields": {
"customfield_10042":"4270d2c6-2e41-413c-97e5-9b05623d9ea0"
}
} 

So in your case add a " after 10001