Error creating issue: Sub-tasks must be created in the same project as the parent.

[Rose Lebel]

We are suddenly getting this error for all our automations and it was working fine just yesterday, no other configuration changes were done recently. Any idea why this is happening?

Error creating issue
Sub-tasks must be created in the same project as the parent. (project)

Appreciate your help, thanks!

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

My guess is that someone may have changed the project key.  Your automation will have been set up to create sub-tasks in project ABC, but that's not there any more.

[Rose Lebel]

Hi Nic, thanks for the prompt feedback!

There were no changes on the project keys on the projects we have, and we are not using sub-tasks for any of our projects so I am confused as to why I would be getting this type of error all of a sudden.

The automations have been working fine yesterday, no major config changes done on the project settings, or automation rules except on one automation rule assigning a cloned ticket to a particular role/user but apart from that, nothing else was changed. 

Still getting this error when I undid the assignee change just to make sure:

Clone issue

Error creating issue

Sub-tasks must be created in the same project as the parent. (project)

[Bill Sheboy]

Hi @Rose Lebel -- Welcome to the Atlassian Community!

For a question like this, please consider posting images of the automation rule and the audit log details showing the error.  Those may provide more context for the community to offer suggestions.  Thanks!

Kind regards,
Bill

[Nic Brough -Adaptavist-]

If the project hasn't changed, then I'm complete with you on the "confused", it's the only thing I can think of that might cause this situation.

Would it be possible to see the Automation that is going wrong?

[Rose Lebel]

Thank you Bill and Nic for your responses.

The automation rule is:

===

When : Issue is transitioned from one status to another

Then: Clone issue into another project.

===

The rule is quite simple and has been working fine for us for a while now, except this afternoon. I created a Jira Support Ticket and I was told it's happening with issues inside an Epic. When I asked why it was working previously given we have Epic links and no sub-tasks from the get go, I was advised that this is an internal bug with Jira.

I was told to add this as a workaround in the rule and it resolved the issue.

"fields":{
"parent":null
},

They mentioned issue is linked to this:

[JSWCLOUD-22457] Clone actions fail to create issue saying Parent issue is needed even though target issue is non-subtask - Create and track feature requests for Atlassian products.

I guess April fool's came in early for me today. :P Thanks for all your help!

[Bill Sheboy]

Thanks for that information, Rose!  This appears to be related to the transition to use "parent" throughout the hierarchy, and move away from "Epic Link": https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048/78

[Nic Brough -Adaptavist-]

I think April fools came early for all of us!

Nice one finding that, I'd cast around and completely missed it!

[Alex Basile]

I also suddenly stared experiencing this today. Thanks for the suggestion to set the parent as null. Worked for me!