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; } } }

Global Automation cant create task

Samuel Imrich

I am having troubles (and tried 1000 ways how to fix) running automation (global) that is triggered upon Project creation. Trigger works perfectly, but i can not create a single issue/task. Everything is blank, out of the box, no custom fields, values etc but i am still getting this error

Error retrieving the issue type fields for project/typeId -

10101/10010

I tried different issue types (they are properly mapped in project), custom fields, ALL fields possible, no difference, every time this error. Cloning the issue works, but not creating from scratch. Also tried making actor as myself (admin) rather than jira automation.

I want to have an automation that will be triggered when a new project with specific name is created, creating a list of tasks for that project automatically.

Accepted answers

Bill Sheboy

Hi @Samuel Imrich -- Welcome to the Atlassian Community!

The likely cause of that symptom is timing (i.e., a racetrack condition) where the Project Created trigger fires before the project configuration (including the issue types) is fully available...leading to the errors you observe.

For workarounds, something needs to happen to slow down the rule a bit after the trigger and before the Create Issue actions. What license level of Jira are you using?

If you are on the Premium or Enterprise level, the Delay action could be used to pause the rule for a while until the configuration completes: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Delay
If you are on the Free or Standard level, that action is not present. Instead you could try performing some actions which take time to slow the rule. This still may not help as the duration needed is unknown, but it is worth a try.
- Use Lookup Issues action to load many issues with JQL, ignoring the results. That would probably add at least 2 seconds of time.
- Use one (or more) Send Web Request actions to call the REST API, such as for an issue search with JQL. (Remember to check the box to allow the rule to continue even if the request fails.)
- etc.

Kind regards,
Bill

All comments

Vishal Biyani_2pr07j

@Samuel Imrich

Can you share the screen shot of the automation that you have created so far?

Jeremiah Rappley

Hey Samuel, have you looked into using the Incoming webhook trigger for your automation rule?

I'm happy to guide you through setting this up!

Samuel Imrich

Screenshot 2025-03-07 151835.jpg

Samuel Imrich

Thanks Jeremiah, but the trigger itself is not a problem, the problem is simple and basic operation which is "just create a task". I have done complicated things in prod, this is just testing in my dev but cant get a simple task being created for no valid reason. Screenshot 2025-03-07 152804.jpg

Vishal Biyani_2pr07j

@Samuel Imrich

Can you try using same project instead of same project as trigger?

Also, not sure if creating a Epic first makes a difference.

In my cloud instance the rule is executing file and creating the issues

Samuel Imrich

Did exactly the same thing, error as usual (but the first ID is the one from Epic) Screenshot 2025-03-07 160827.jpg

Screenshot 2025-03-07 160725.jpg

Bill Sheboy

Hi @Samuel Imrich -- Welcome to the Atlassian Community!

For workarounds, something needs to happen to slow down the rule a bit after the trigger and before the Create Issue actions. What license level of Jira are you using?

If you are on the Premium or Enterprise level, the Delay action could be used to pause the rule for a while until the configuration completes: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Delay
If you are on the Free or Standard level, that action is not present. Instead you could try performing some actions which take time to slow the rule. This still may not help as the duration needed is unknown, but it is worth a try.
- Use Lookup Issues action to load many issues with JQL, ignoring the results. That would probably add at least 2 seconds of time.
- Use one (or more) Send Web Request actions to call the REST API, such as for an issue search with JQL. (Remember to check the box to allow the rule to continue even if the request fails.)
- etc.

Kind regards,
Bill

Samuel Imrich

Hey Bill, Thanks for your answer!
I tried delaying the execution by adding three dummy web actions just to prove the concept (and wait till response is received). There was more than 30 secs of delay between project creation and Create issue state but it failed as well. Or should it wait longer? Screenshot 2025-03-07 183428.jpg

Bill Sheboy

Just to confirm, what type of project is this for: company-managed or team-managed?

If this is for a team-managed project, their issue types are unique for each project. That is, the internal ID for the issue type is different even when the names are the same.

The saved ID values in the Create Issue actions will not work as they are unknown when the rule publishes and they cannot be updated dynamically. (At least that was not possible when I tried this scenario a year ago.)

I believe the only workaround is to use the Send Web Request action to call the REST API and...

get the issue type hierarchy for the new project by its ID: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-projectid-hierarchy-get
extract the issue type ID needed from the web response
create the issue that ID, again using the REST API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post

This approach will likely eliminate the need for other delaying rule actions for the racetrack condition.

Samuel Imrich

Uff, thats a really complicated workaround for such a simple task, but you are correct. When i tried changing the project type to Company managed, automation ran without any issues, so thanks for that! At least now I know where to look.

I am trying to build the workaround with the API you proposed and keep you posted if that helped, but i am a bit dissapointed that such a trivial thing can not be done with "out of the box" solution.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud