Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,176
Community Members
 
Community Events
184
Community Groups

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

Warren Singzon
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 04, 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.jpgautomation rule 1.jpgpermission.jpgerror 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.
Apr 06, 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
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 06, 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.
Apr 07, 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. 

Suggest an answer

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

Atlassian Community Events