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.

[Olga Cheban _TitanApps_]

Hi, @Gretchen !

That error usually points to a mismatch between the issue type or field IDs in your rule and what the target project actually supports. Automation rules that hard-code type/field IDs tend to break when the project setup differs even slightly. This can also be a timing issue, as the others pointed out earlier.

Since your goal is really "every new project starts with the same 8 epics," there's a simpler route worth considering. For this purpose, I can recommend our solution, Smart Templates for Jira. It lets you save any set of work items as a template. 

In your case, you can: 

• Create your 8 epics once
• Save them as a reusable template
• Make this template Global (so that it's accessible across projects/spaces)
• Generate the whole set from the template whenever you need it - manually or with automation.

Here's a practical example of this approach: a project kick-off template. In this case, it's a task with subtasks and checklists, but it can be any set of work items. You can include child work items, task descriptions, pre-filled fields, variables, and more.

Smart Templates allow you to create tasks from templates automatically with its built-in Scheduler. It can also be used together with Automation for Jira, which is more relevant in your case. With this automation, you avoid the fragile field mapping you're hitting right now.

To set up this automation, you will need to generate a webhook link for your template. Then, you can create a Jira Automation rule with the "When project is created" trigger and a "Send web request" action pointing to that webhook URL. As a result, every new project will get your 8 epics automatically.

Here's what that automation rule looks like:

You can read more about this use case in my article Project Kickoff Template.

Smart Templates work during a free Jira trial as well, so you can test the flow before deciding. There is also a free tier available, so you can try it out without any strings attached.

I hope this helps. Let me know if you have any questions!

[Monika Ambrozowicz_Seibert_]

Hi @Gretchen, @James Gamble and @Germán Morales have explained the issue already. This happens frequently when chaining issue-creation actions in Jira Automation because the project context or the issue type ID isn't available or is being referenced incorrectly.  

If you are open to a third-party app, Templating.app has Space Templates specifically designed for this: You define a project template that includes a preset collection of issues (including epics with predefined summaries, descriptions, and field values), and whenever someone creates a new project from that template, all 8 epics are created automatically, no automation rule debugging required. Non-admin users can also create projects from templates, which removes the common bottleneck. Full disclosure: I work with a team behind the app, but I've seen users for whom it genuinely solved such a problem. 

If you want to stick with native Jira Automation, double-check that the issue type ID in your rule matches what your instance uses for epics, and that the project key is being passed correctly into each "Create issue" action. If you want to give Templating.app a try - I'm here if you have any questions. 

[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]

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.