You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
As I've dove into JPD, I'm discovering this is the tool I've been dreaming of for the last few years ;) I'm pretty excited!
My company is new to "doing product management correctly" so we've incorrectly been creating issues / stories / tickets for EVERY idea over the last 10 years. All of these are within our dev queue, which is causing confusion. They don't belong there!
My goal: to transfer these ideas INTO JPD. However, I don't want to lose the history. I also know that some of these issues are duplicative.
Any suggestions on what to do? Close all the current issues (that are not actual dev to-dos) and recreate new, linked issues in JPD? Simply Move all issues into JPD?
Has anyone tried something like that? What was your approach?
Hi ! I have been struggling a lot with that (have created a topic here)
So I have created them in JPD from a csv export but lost a lot of information and need to update them individually to put back the associated insights in the right place, it's a bit time consuming but I have not found a better way to do it
@Louise Baker @Sara Di Meglio @Alexis Marticorena as you know Jira Product Discovery is currently in beta, and as part of that we took a few shortcuts and have a few limitations. One of those is a way to import ideas into the tool.
As of today I would recommend doing the following:
The reason for this is that this way you are sure not to lose any data as the Jira Software issues are still here - vs with bulk move a few things can go wrong (fields not matching between the source and target project, field type not supported in the discovery project, etc.)
That being said, if all you care about is the following being preserved:
Then a bulk move of these issues should work fine. I'd recommend testing on a couple of ideas first.
But if you used lots of custom fields, you might run into issues with the bulk move.