nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

passing values from one project to another with automation

Vasco

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?

Comments

Vasco

I just found this indication, I will try out:

Vasco

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.

Vasco

in the end I noticed that I didn't had the fields correctly placed in the source task.
Newbie stuff.

Tom Bowden

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".

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

new-to-jsm