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

transition to JDP

secutechconsultingservices

Hello,
We currently utilize Jira Work Management to manage product engineering ideas, specifically under the "idea" issue type, with a straightforward workflow (open, in progress, and done). We're considering a transition to Jira Product Discovery and are looking to import all ideas into JDP with a completely new workflow.

I'm aware that we might use CSV export/import or a bulk move for transferring the data. However, could you guide me on how to transfer Jira issues between Jira Work Management and JDP when the workflow statuses differ? Also, could you please outline the steps I should follow to ensure a smooth transition?

Thanks for the support in advance

Accepted answers

Muhammad Khan_q2nnw0

To transfer Jira issues between Jira Work Management and Jira Product Discovery with differing workflows, use CSV export/import or bulk move options. Define mapping between old and new workflows. Ensure fields compatibility and consider testing data integrity before final transfer. Communicate changes to users and provide training if needed. Update any automation or integrations accordingly for a smooth transition. For more information about SASSA srd status check click on this link. https://sassasrdstatuscheck.net/

Ste Wright

Hi @secutechconsultingservices

I would bulk move over export/import, to ensure the issue history remains intact. You can just bulk move issues between JWM and JPD like any other Project.

To move issues, you will need the JPD Project set-up first.

---

To do this...

Go to Filters > View all issues
Search for the relevant issues
Next, in the top-right, select the breadcrumbs button (...)
From the select list, choose Bulk change all N issue(s)
On Step 1, select the issues to move. You can select "all" using the checkbox in the title row
On Step 2, select the option Move issues
On Step 3, Select your JPD Project, and the relevant Issue Type (eg. Idea)
On the next screen, map existing statuses to new statuses
Next, on the fields screen, populate/map required field(s) here
On Step 4, check the mapping - then press Confirm to complete the move

---

A few notes...

I found in (9) that some fields were marked as mandatory, but I didn't populate any of them and pressed next - and it still let me move the issue(s)
As JPD Projects are based on Team-managed Projects, and do not yet utilise global fields, it is likely fields like Story Points, Components, etc will become NULL during the move. You might be offered the option to map this data across as part of (9), depending on the field

---

For (2) in the notes list, you could...

Export all issue field data prior to the move
Move the issues to the new JPD Project
Re-export the data
Map the field data to the new Issue Keys, based on Issue ID
Re-import the field data into your new fields post-move

Whilst the Issue Key will change when moving between Projects, the Issue ID should remain static and will be the common denominator between the two exported lists.

See more information on CSV imports on this help page

---

Let us know if you need any further advice, or more detailed instructions for exporting/importing the data!

Ste

All comments

Muhammad Khan_q2nnw0

Ste Wright

Hi @secutechconsultingservices

I would bulk move over export/import, to ensure the issue history remains intact. You can just bulk move issues between JWM and JPD like any other Project.

To move issues, you will need the JPD Project set-up first.

---

To do this...

Go to Filters > View all issues
Search for the relevant issues
Next, in the top-right, select the breadcrumbs button (...)
From the select list, choose Bulk change all N issue(s)
On Step 1, select the issues to move. You can select "all" using the checkbox in the title row
On Step 2, select the option Move issues
On Step 3, Select your JPD Project, and the relevant Issue Type (eg. Idea)
On the next screen, map existing statuses to new statuses
Next, on the fields screen, populate/map required field(s) here
On Step 4, check the mapping - then press Confirm to complete the move

---

A few notes...

I found in (9) that some fields were marked as mandatory, but I didn't populate any of them and pressed next - and it still let me move the issue(s)
As JPD Projects are based on Team-managed Projects, and do not yet utilise global fields, it is likely fields like Story Points, Components, etc will become NULL during the move. You might be offered the option to map this data across as part of (9), depending on the field

---

For (2) in the notes list, you could...

Export all issue field data prior to the move
Move the issues to the new JPD Project
Re-export the data
Map the field data to the new Issue Keys, based on Issue ID
Re-import the field data into your new fields post-move

Whilst the Issue Key will change when moving between Projects, the Issue ID should remain static and will be the common denominator between the two exported lists.

See more information on CSV imports on this help page

---

Let us know if you need any further advice, or more detailed instructions for exporting/importing the data!

Ste

secutechconsultingservices

Thank you very much, Stephen. I'd like to clarify that I do not intend to move the issues from JWM, instead, I need to copy them. In other words, I do not wish to disturb the existing setup in JWM. I simply want to copy all issues to JDP to demonstrate its capabilities to the Products VP

secutechconsultingservices

Thanks a lot Muhammad. I don't want to alter the current setup in JWM. Instead, I'd like to duplicate all issues to JDP to showcase its features

secutechconsultingservices

I'd like to clarify that I do not intend to move the issues from JWM, instead, I need to copy them. In other words, I do not wish to disturb the existing setup in JWM. I simply want to copy all issues to JDP to demonstrate its capabilities to the Products VP

secutechconsultingservices

@Ste Wright thank you very much, Stephen. I'd like to clarify that I do not intend to move the issues from JWM, instead, I need to copy them. In other words, I do not wish to disturb the existing setup in JWM. I simply want to copy all issues to JDP to demonstrate its capabilities to the Products VP

Ste Wright

Hi @secutechconsultingservices

Assuming you don't have an App that can do this, I'd probably suggest export/import.

Do you need specific instructions on how to do that? If yes, is there any specific custom configuration/data which is important to copy from JWM?

Ste

Well Jalal

That’s a common question when moving to Jira Product Discovery. JDP does not use classic Jira workflows, so statuses like Open or Done do not carry over directly. Instead, ideas are tracked using fields such as Idea status. The easiest approach is to export your ideas from Jira Work Management using CSV, then import them into JDP and map the old statuses to the relevant JDP fields during the import. Set up your JDP fields and statuses first so you know exactly where each value should go. It’s a good idea to test the import with a few issues before moving everything. Once the data looks right, you can stop using or archive the old project to avoid confusion.

kh-federico

Hi Well Jalal,

This topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have additional questions, we encourage you to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our Community Guidelines.

Thanks!

Welcome!

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