Error when creating tickets via automation in Jira: Problems with fields not defined in the screen

[Siggi Pfaff]

Hello dear Atlassian Support :)

I have a problem here and would like an explanation please.

Let me briefly explain the problem:
I would like to use automation to create a new ticket with a set request type in another project - but since this function is very limited in terms of filling in additional fields, I have to use the “Additional fields” option.
But now I have the problem that I often run into the same error if I have not defined fields in Screen. I know that these are required if you want to set them and the person executing the automation, i.e. the actor, does not have sufficient rights, so this automation fails.
However, this should not fail if “Jira for Automation” is the actor, according to another Atlassian employee 3 years ago:
https://community.atlassian.com/t5/Jira-questions/Re-Re-Can-Automation-rules-edit-a-hidden-field/qaq-p/1802745/comment-id/652482#M652482

My automation is set up so that “Jira for Automation” is the actor of this automation. Unfortunately, I still run into an error with the fields that are not set in the screen (Fields 13133, 12603, 14816). What is the reason for this?
What is the difference to the Edit-Issue, which can fill fields that are not on the screen, should the automation be executed by “Jira for Automation”?

Kind regards,
Siggi

[Marc - Devoteam]

Hi @Siggi Pfaff 

Welcome to the community.

To be clear at first, the community is not Atlassian Support.

Is a forum where enthusiastic people (Atlassian product users) try to help each other.

Your issue relates to the fact that the screen used to create an issue doesn't have the fields you want to set in the automation on the screen.

Then you also would not need the needed to use JSON format.

Based on the https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ from the linked community post, you need to retrieve the createmeta or editmeta via the links in that article.

Example:

{

  "fields": {

     "Summary": [{ "set": "{{triggerIssue.summary}}" }]

                }

}

See also post: https://community.atlassian.com/t5/Jira-questions/Automation-for-Jira-Update-Json-field/qaq-p/2018341 

[Siggi Pfaff]

Aha, I see!

Nevertheless, it doesn't change the fact that I have to use the JSON format to set the data, since creating a ticket with a certain request type, as described above, is very limited (two fields in total).
I need to set quite a few fields, not just two, so the JSON operation is essential.

Furthermore, I am explicitly asking why it is possible to set these fields via Edit-Issue when Jira for Automations is selected as the actor, but it is not possible to do so via JSON.

The link I included shows that Jira for Automations can bypass the screen check.

[Marc - Devoteam]

Hi @Siggi Pfaff 

Yes it can, but no in the way you have setup your JSON, that is not possible.

See the links I provided about createmete or editmeta.

Your JSON needs to be different, you need to use "set" actions, but you need to check if the option is available for that field?