Clone story point estimate field
Asked by Caitlin.Pedersen:

Hi,

I'm trying to set up an automation where I clone an issue from a company managed project to a team managed project.

It is important to me to clone the field Story point estimate.

However, the field Story points seems to be related to the company managed projects and the field story points estimate seems to be related to the team managed projects.

Even though I can add both fields to my issue layout in the company managed project, I can only add the Story point estimate field to the team managed project.

Is there a way I can make the story point estimate show in my team managed project when I clone the issue?

This is my automation:

![Jira question.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/345988iA975127FD4DCCD84/image-size/large?v=v2&px=999 "Jira question.JPG")

Thank you very much!


Answers:
author: Adri?n Garc?a Gonz?lez
body: Hi [@Caitlin.Pedersen](/t5/user/viewprofilepage/user-id/5459596),

I understand your problem, in fact it seems to be something that many others have encountered....

The Story Points field is only available in Company-managed projects while the Story point estimate field is available in Team-managed projects. After this clarification let's go with your problem, in order to have the Story Points value in the cloned issue you can copy it at the time of cloning, to do this you must use this json in the Clone block:

```
{
"fields": {
"Story Point estimate":{{triggerIssue.Story Points}}
}
}
```

Screenshot of my tests:

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

After this the cloned issue will have in the Story point estimate field the value that the source issue had in the Story Points field!

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

Let me know if it helps, best regards!

comments: author: Caitlin.Pedersen
body: Hi [@Adri?n Garc?a Gonz?lez](/t5/user/viewprofilepage/user-id/4961741)

Thanks a lot.

I just tried it and it worked perfectly :)

Best regards!


author: Clara Belin-Brosseau
body: Hello [@Caitlin.Pedersen](/t5/user/viewprofilepage/user-id/5459596)

If you're seeking for an easy way to **clone an issue and map two different fields across projects,** I suggest trying 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_2805225&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).

You can check our guide [here](https://doc.elements-apps.com/copy-and-sync-jira-cloud/create-a-mapping-of-jira-fields-between-two-issues?&utm_source=community&utm_medium=answer&utm_campaign=question_2805225&utm_keyword=CS&utm_vendorID=4952).

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


author: Luka Hummel - codefortynine
body: Hi [@Caitlin.Pedersen](/t5/user/viewprofilepage/user-id/5459596),

To address the challenge of cloning the **Story points** field from a company-managed project into the **Story point estimate** field in a team-managed project, our app [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2805225) can be a great solution. It allows you to deeply clone issues, including custom fields like Story Points, and ensures that all important data is transferred seamlessly between projects, even when field names differ.

With the [Field Editor](https://documentation.codefortynine.com/deep-clone-for-jira/field-editor?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2805225) feature you can copy the value of the **Story point** field to the **Story point estimate**field when cloning the issues.

![2024-09-09 11-18.png](https://community.atlassian.com/t5/image/serverpage/image-id/346254i8C3828723772233B/image-size/large?v=v2&px=999 "2024-09-09 11-18.png")

You can also integrate Deep Clone in your existing Jira Automation. You can read more [here](https://documentation.codefortynine.com/deep-clone-for-jira/jira-automation?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2805225).


Tags: cloud

jira-work-management

jira-work-management-cloud