How to clone issues from JSM to JPD project
Asked by S?awomir Ja?oszy?ski:

I want to prepare automation in which an issue created in jira service management will be cloned to a project in jira product discovery. ![JSM2.png](https://community.atlassian.com/t5/image/serverpage/image-id/344765i4D3FB8531128FDD3/image-size/large?v=v2&px=999 "JSM2.png")Unfortunately, there is a problem with the issue type with the standard command. For the issue type in JSM, I do not have the option to add an "Idea" from JPD  

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

How can I solve this problem?


Answers:
author: Nick H
body: Hi [@S?awomir Ja?oszy?ski](/t5/user/viewprofilepage/user-id/5413215) ,

It sounds somewhat similar of an issue to this other [Community question](https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Create-issue-automation-failing-with-quot-Please-select-a-valid/qaq-p/2772151) trying to do something similar.

As I mentioned in that same question:
> We've noticed some customers' A4J user not being granted JPD permission. This isn't so much a bug, but something we're working on correcting.
>
> Regardless, you'll want to open a ticket with JPD support so they can grant your A4J user with JPD permission. The A4J user cannot be granted permission from your end.
>
> You can do that within JPD under the*Give Feedback* tab \>\> *Get help from the support team* , or [HERE](https://support.atlassian.com/contact/).

A workaround could be adjusting the [Actor](https://support.atlassian.com/cloud-automation/docs/what-is-a-rule-actor/) of the automation that has JPD permission to see if results vary and/or are successful.

Otherwise we should be able to help if you reach out to JPD support so we can take a investigate further.

comments: author: S?awomir Ja?oszy?ski
body: [@Nick H](/t5/user/viewprofilepage/user-id/2540930)

Changing the actor was a bullseye that solved the cloning problem. Thank you for your time and describing the solution.

By the way, I have one more question:  
After I clone an issue from JSM to JPD and link them, I would also like to set up an automaton that will add them as a delivery ticket from the linked issue from JSM.

The goal is to link some fields like start date or due date to the original ticket.


author: Luka Hummel - codefortynine
body: Hi [@S?awomir Ja?oszy?ski](/t5/user/viewprofilepage/user-id/5413215)

To clone issues from Jira Service Management (JSM) to Jira Product Discovery (JPD), you can use our app [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2799278). Deep Clone allows you to clone issues across different projects, including between JSM and JPD. It also enables you to customize the cloning process, ensuring the correct issue types and fields are copied over. We have a detailed documentation site [here](https://documentation.codefortynine.com/deep-clone-for-jira/how-to-migrate-your-projects-to-jira-product-disco?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2799278) on how to clone issues from other Jira project types to JPD.

comments: author: S?awomir Ja?oszy?ski
body: Thank you for your suggestion. I have used the add-on before and I am happy with it, but the number of paid subscriptions far exceeds the budget, so I am looking for basic solutions.


author: Amina Bouabdallah
body: hi there! can you tell us a little bit about the use case leading you to want to auto-populate a JPD idea from a JSM ticket?

comments: author: S?awomir Ja?oszy?ski
body: [@Amina Bouabdallah](/t5/user/viewprofilepage/user-id/5343033)   
In JSM we currently have different issue types set. Some are regular service requests with a set SLA, and some are ideas that should appear on the roadmap in JPD. The roadmap is supposed to help filter ideas in an easy way and prioritize them accordingly, depending on the selected filters.


Tags: clone

issue-type

jsm