Automation: Could not find create meta data for project/typeId

[G. De Fazio]

Hi, I create an automation that create a ticket in a Jira Software project:

- I have a ticket in Jira work (Project id: 10109)

- I change the status of this ticket in "Escalated"

- the automation must create a ticket in jira software (Project  id: 10108).

The problem is that the automation answer with this error:

can anyone help me with this issue?

Thanks,

Giuseppe.

[Jack Brickey · Accepted solution]

Could you please share screenshots for your automation rule and the audit log that results when an issue is escalated?

[G. De Fazio]

Hi Jack,

     thanks for your answer.

Here the screenshot of the automation and the transcription of the log:

------------------------------ LOG -------------------

Dettagli azione:

Condizione ticket
Ticket risolti:
SILRL-5

Azione log
Log
Progetto: 10108

Blocco If
Ticket risolti:
SILRL-5

Crea ticket
Impossibile creare metadati per l'ID progetto/tipo -
SmartProjectBean{source=Project{self='https://liguriadigitale.atlassian.net/rest/api/2/project/10109', id=10109, key='SILRL', name='SIL_RL - Supporto L2 per SIL', description='null', avatarUrls={48x48=https://liguriadigitale.atlassian.net/rest/api/2/universal_avatar/view/type/project/avatar/10421, 24x24=https://liguriadigitale.atlassian.net/rest/api/2/universal_avatar/view/type/project/avatar/10421?size=small, 16x16=https://liguriadigitale.atlassian.net/rest/api/2/universal_avatar/view/type/project/avatar/10421?size=xsmall, 32x32=https://liguriadigitale.atlassian.net/rest/api/2/universal_avatar/view/type/project/avatar/10421?size=medium}, issuetypes=null, projectCategory=ProjectCategory{self='https://liguriadigitale.atlassian.net/rest/api/2/projectCategory/10001', id=10001, name='Livello 2', description='Progetti di supporto Lv2'}, email='null', lead=null, components=null, versions=null, projectTypeKey='business', simplified='false'}} Project{self='https://liguriadigitale.atlassian.net/rest/api/2/project/10109', id=10109, key='SILRL', name='SIL_RL - Supporto L2 per SIL', description='null', avatarUrls={48x48=https://liguriadigitale.atlassian.net/rest/api/2/universal_avatar/view/type/project/avatar/10421, 24x24=https://liguriadigitale.atlassian.net/rest/api/2/universal_avatar/view/type/project/avatar/10421?size=small, 16x16=https://liguriadigitale.atlassian.net/rest/api/2/universal_avatar/view/type/project/avatar/10421?size=xsmall, 32x32=https://liguriadigitale.atlassian.net/rest/api/2/universal_avatar/view/type/project/avatar/10421?size=medium}, issuetypes=null, projectCategory=ProjectCategory{self='https://liguriadigitale.atlassian.net/rest/api/2/projectCategory/10001', id=10001, name='Livello 2', description='Progetti di supporto Lv2'}, email='null', lead=null, components=null, versions=null, projectTypeKey='business', simplified='false'}/10002

Collega ticket
Errore durante il collegamento di ticket
: È richiesto almeno il parametro 'ID' o 'chiave' per identificare un ticket.

Blocco If
Ticket risolti:
SILRL-5

Crea branch regola/ticket correlati
Nessun ticket correlato trovato.

-------------------- END LOG ----------------------

Giuseppe.

[Bill Sheboy]

Hi @G. De Fazio 

Adding to Jack's answer...

The error seems to indicate a problem with issue linking; specifically that the value used to link the issues is invalid.

Please show the details of where the issue link is attempted, and the source of the value used to link the issues.  That may indicate the cause.

Kind regards,
Bill

[G. De Fazio]

but the issue is not created, the error is in creation step, the one before the link.

Giuseppe.

[G. De Fazio]

issue link

issue creation

[Bill Sheboy]

Thank you...Would you please show the details of the issue create action?  There seems to something the create is doing which is related to issue linking.

[Bill Sheboy]

In automation rules, things which happen at different points may not be visible later.  For example, when a variable is created inside of a branch or condition.  This is known as rule scope.

You appear to be using an if/else condition structure, and inside of that creating a variable named Progetto (i.e., Project).

That is also the name of an existing smart value for the issue, and so the rule could be encountering a problem: referencing the re-use of that term, referencing whatever value you are setting into it, and in the scoping .

It is generally a good idea to always name created variables so they cannot collide with other names, such as with a prefix like varProgetto.

Let's try this: rename your variable so it will not collide AND add a write to the audit log with the value immediately before the second if/else condition (where the task is created).  I believe this will show the value is empty.

[G. De Fazio]

Solved!

- I collapsed the 2 "if" in 1

- I moved the issue creation in the same if

and now it worked!

Thanks a lot,

Giuseppe.