Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Migrate existing tickets from a jira software project ( cloud ) to jira product discovery proj


Can I migrate existing tickets from a jira software project ( cloud ) to jira product discovery project.


3 answers

1 accepted

3 votes
Answer accepted
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 02, 2022
0 votes
Curt Holley
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 01, 2022

Because Product Discovery projects are "team managed" (under the hood) and it is likely the Jira software tickets are from company managed projects, you will need to be careful. Especially as there will likely be a number of fields that are different between the two.
See: Migrate between team-managed and company-managed projects | Jira Work Management Cloud | Atlassian Support for guidance.

But to be honest, I wouldn't do it. I would create "Ideas" in the JPD project and link to the Jira software tickets that way.

We have an "idea" issuetype in our sw products that we usually convert to stories or tasks if we choose one to work on. So moving them over makes perfect sense for us! There aren't any fields we might lose. Going forward we would for sure create the ideas directly in the JPD project. 

(Just giving insight as to why someone might want to move issues over)

Fwiw, I've done countless imports into JPD, because in my situation we had over 30 Jira Software projects (cloud) I needed to load into JPD. It was a time consuming exercise that required a lot of data cleanup in multiple spreadsheets. I was able to do to it eventually, but it took me several weeks to do.

One thing I wish I had known earlier in the import process was to define a field linking the old tickets to the newly created ones. I found a way to do it, but not after importing over 10 projects. 

I highly recommend doing 'test' imports (with smaller data sets) to see how the data lands in JPD and to ensure that you have all of your necessary fields before doing a massive import job. 

Also, I learned the hard way that I hit endpoint limits, bringing down my company's Jira instance. (You can only create a certain number of Jira tickets within a certain period of time. I've found it's roughly around 500 tickets each hour or so.)

I don't see why not. 

Advanced Issue Search > Bulk Edit > Move

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events