Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Need help to understand this error -Could not find create meta data for project/typeId - 10003/10003

Warren Singzon April 4, 2023

I created an automation rule that will create a subtask when a story transition to a certain status. I have also made sure the automation have permission to edit issues. BUt I always get this error "Could not find create meta data for project/typeId - 10003/10003".

I don't understand why this doesn't work. I have the same automation rule in another jira instance and its working. automation rule 2.jpg automation rule 1.jpg permission.jpg error 1.jpg

 

 

 

 

1 answer

1 accepted

0 votes
Answer accepted
Magdalena Zhisheva
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 6, 2023

Hi @Warren Singzon , 

Can you try to drag the action to be one level above, i.e. not part of the if condition but as part of the action line?

Screenshot 2023-04-06 at 17.16.02.png

Warren Singzon April 6, 2023 edited

Thank you very much for the reply. With some help, the culprit was a required field set in the field configuration settings. Even I didn't use the field in the screen, the setting was global for all screens. It blocked me to create an issue until I set that required field.

Magdalena Zhisheva
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 7, 2023

Hi @Warren Singzon , 

Glad to here that you solved the problem!

Global required fields are really tricky as you must configure all create screens in the CMP to have that field. 

Tom Mina-Coull June 14, 2023

@Warren Singzon Which field was it? I am having the same issue and I can't seem to find any fields that could be blocking it. Pretty sure the only global required fields are Issue Type and Summary, both of which I have filled in.

Warren Singzon June 14, 2023

@Tom Mina-Coull it was a custom field that I created for other screens but I didn't realize that setting it required made it a global setting. So when I created a new screen, even if I'm not using the field it still looks for it as required because I used the same field configuration scheme.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events