Automation (When new space is created add 8 epics to the space) - Error retrieving the issue type f

[Gretchen]

Hello,

I am trying to create a global automation so when a new space is create that 8 epics are automatically added to the space. However I keep getting this error: 

Error retrieving the issue type fields for project/typeId -10141/10000

Just to note: I am using a free trial at the moment to see if this is the right software for my team. A lot of our spaces would start with the same 8 epics so I would like to be able to automate this.

[James Gamble]

Hola Gretchen,

This sounds like a timing issue with the “space created” trigger. When a new Jira space/project is created, the automation trigger can fire before Jira has finished applying the project configuration, including work types, screens, fields, and permissions. So the new space exists, but Automation can’t yet retrieve the Epic field metadata, which can produce an error like:

Error retrieving the issue type fields for project/typeId -10141/10000

There’s a very similar Community thread here where the accepted answer points to that same timing/race-condition problem: https://community.atlassian.com/forums/Jira-questions/Global-Automation-cant-create-task/qaq-p/2965366

Since you’re on Premium, I’d try adding a Delay action immediately after the “Space created” / “Project created” trigger. Start with something like 1 or 2 minutes, then create the 8 epics after the delay.

Atlassian’s automation actions page includes the Delay action here: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/

Thanks,

James

[Germán Morales _ Hiera]

Welcome to the Community, @Gretchen .

That error almost always means the rule's actor can't create issues in the target space. On a global rule that fires when a brand-new space is created, the actor has no Create Issues permission in that just-born space yet, so the action can't even read the epic's fields, which is the message you're getting. The fix Atlassian documents is to add the rule's actor to the Create Issues permission of the project; if the actor is Automation for Jira, grant the project role atlassian-addons-project-access on Create Issues. To cover every new space, set this on the shared permission scheme those company-managed spaces use. Steps are in resolve "Error retrieving work type fields".

The negative project id in your message (-10141) points to a second, known factor: the create-space trigger can fire before the new space has finished provisioning its work types, so the create action resolves to a space that isn't ready. Make sure that action targets the smart value of the newly created space rather than a fixed project, and if it still races, add a short delay before the create step.

One thing worth knowing before you invest more here: custom space templates copy configuration like boards, work types, fields and workflows, but not work items, so a template alone won't seed the 8 epics. Automation is the right tool for the epics; many people pair a template for the base setup with a rule like yours to create the starting epics.