Automation incompatibale
Asked by Lianne Geerlings:

**Goal**: Have a software project to be used as a Template project and

When a certain user is creating a new software project, an automation should run and create several tasks in that new project.

I have spend hours arranging this but I am not getting this working.

![Scherm?afbeelding 2024-08-20 om 11.24.07.png](https://community.atlassian.com/t5/image/serverpage/image-id/342681i33441915575C86DD/image-size/large?v=v2&px=999 "Scherm?afbeelding 2024-08-20 om 11.24.07.png")

Even creating another type of automation to clone tickets from one project to another is giving me an error message like: "

Can not create issue in project/issue type  

While the same issues type are in both projects.


Answers:
author: Luka Hummel - codefortynine
body: Hi [@Lianne Geerlings](/t5/user/viewprofilepage/user-id/5027449),

To simplify copying your template and overcome issues like incompatible components, you might find our app [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2789135) helpful. It allows you to clone whole projects, issues, including subtasks and their hierarchy.

You can read more how to use Deep Clone to clone your template projects [here](https://documentation.codefortynine.com/deep-clone-for-jira/article-a-story-about-working-with-template-issues?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2789135).


author: Clara Belin-Brosseau
body: Hello [@Lianne Geerlings](/t5/user/viewprofilepage/user-id/5027449)

If you're seeking for an easier way to **automatically create issues from a template project** , you can try our app [Elements Copy \& Sync](https://marketplace.atlassian.com/apps/1211111/elements-copy-sync-clone-jira-issues?tab=overview&hosting=cloud?&utm_source=community&utm_medium=answer&utm_campaign=question_2789135&utm_keyword=CS&utm_vendorID=4952) that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

![Elements Copy & Sync - Copy issue from one project to another.png](https://community.atlassian.com/t5/image/serverpage/image-id/342754i14223F9215AC735A/image-dimensions/360x266?v=v2 "Elements Copy & Sync - Copy issue from one project to another.png")

You can check our guide [here](https://doc.elements-apps.com/copy-and-sync-jira-cloud/copy-all-issues-from-one-project-to-another?&utm_source=community&utm_medium=answer&utm_campaign=question_2789135&utm_keyword=CS&utm_vendorID=4952).

The app is for **free during 30 days** (and it stays free under 10 users).

comments: author: Lianne Geerlings
body: Thanks for the suggestion [@Clara Belin-Brosseau](/t5/user/viewprofilepage/user-id/5326232) it looks really great, but the pricing after those 30 days is way to much for the number of people who are going to actually use it.   

Would be nice if payments could be based on the user role instead of the number of users in the organization ;-)


author: Clara Belin-Brosseau
body: Yes I understand your point [@Lianne Geerlings](/t5/user/viewprofilepage/user-id/5027449) unfortunately, its not on us but on Atlassian to decide how to calculate the prices.

I hope you'll find the right solution to your task creation problem :)


author: Leo Prakash_CodeForMe_
body: Hey [@Lianne Geerlings](/t5/user/viewprofilepage/user-id/5027449) ,

If I'm not wrong you want to check if the user who created is part of PMers group then you want to perform the tasks creation

if so, the condition should "***Initiator*** " or "***User who triggered the event***" is in so and so group instead of Reporter is in group

Reporter is for Issue object but automation receives project object which doesn't have reporter field.

Hope this gives you some idea

Regards,

Leo

comments: author: Lianne Geerlings
body: Thanks for bringing the idea [@Leo Prakash_CodeForMe_](/t5/user/viewprofilepage/user-id/5333216)

Unfortunately if I replace it to " Initatator" the audit log says  

" Can't run component as it requires issue(s) in the context. More than likely you have a trigger that doesn't insert issues into the rule chain. e.g. Scheduled rule not running a JQL query. Creating an issue does not put an issue into the context, you have to branch on it to update it."

I am not familiar with using branches, do you?


author: Leo Prakash_CodeForMe_
body: It's quite easy, you can refer below screenshots  
in clone component, make sure you pass {{project.id}} variable to clone the tickets to newly created project

<br />

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/342685i0C082387CBCF4077/image-dimensions/504x238?v=v2 "image.png")  

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/342686i8A19F46713B89EC3/image-size/large?v=v2&px=999 "image.png")


author: Lianne Geerlings
body: Thanks so much [@Leo Prakash_CodeForMe_](/t5/user/viewprofilepage/user-id/5333216) this start making sense to me and will practice as suggested to see if this would full-fill my needs!


author: shiva kumar Gosul
body: your condition in automation must be specific users and add their name

comments: author: Lianne Geerlings
body: Hello [@shiva kumar Gosul](/t5/user/viewprofilepage/user-id/4674204) unfortunately that does not do the trick   

It still gives an error that I am usung incompatible components.


Tags: cloud

jira-cloud