Hi!
We have built an automation for one project and set the parent issue to be the trigger issue, all works well like this, even when we change the Issue type the "Parent issue" drop-down box is hidden but the rule works ok.
Now when we change the destination project and maintain the issue we do not get any values all we have is the error " Could not find create meta data for project/typeId - 10013/10009"
On a brand new automation the issue is created successfully but they are all empty, no option to chose the parent issue.
What I'm doing wrong?
Community moderators have prevented the ability to post new answers.
Some what after re-running the automation, I noticed that the main difference is when the trigger is a custom subtask it fails, if the trigger is a custom issue I can use automation to create a ticket with all values to another project and another issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vasco, please can you explain? I'm having the same issues on mine. I'm trying to use automation spin up a load of epics automatically in a completely blank new project.
I have global settings so my rule applies to all projects (presumably including any new project I decide to create). But when I create a new project, then manually trigger a rule from an issue (to be run in "same project as trigger") I get the same error you had above:
" Could not find create meta data for project/typeId - 10013/10009".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tom;
It's been a while since this happened.
But I will have to revisit soon because I'm having that same error again.
Let me refresh my memory first.
You can start by checking if object "10009" is available for both projects (10013 and the other)
BR
Vasco
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tom Bowden - did you get a solution to your issue? I have the same troubles when changing an automation rule to global settings: for one project, all works fine. then i change the rule to a global rule - it doesnt work anymore - i get your error-message. thanks for helping me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get the most out of Jira Service Management
Solve customer problems efficiently and deliver outstanding service experiences.
Learning Path
Adopt ITSM practices to deliver exceptional service
Become familiar with the principles and practices that drive ITSM. Then, learn how to configure and use Jira Service Management to implement them.
Atlassian Certified Associate
Jira Service Management Agent Essentials certification
Prove you know what's essential to providing efficient and resolution-focused service in Jira Service Management.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.