How to backup JPD data?

[Deleted user]

Ok JPD team, you've made a great product that's been very successfully used and adopted at our company. And as you're coming out of beta, it's time to solve big kid (as opposed to infancy) problems. How can I currently backup my JPD data, in a way that could be restored in case of some major outage/failure?

Happy to have it be a complete hack for now, until you can provide more official support like in other jira projects.

Any script examples you can share, or other methods, so we're not at risk of permanently losing data?  

p.s. good, informative preso @Tanguy Crusson thanks for sharing it!

[Carlos Garcia Navarro]

Hi @Shawn_Giese , 

I'm not sure I understand, could you please elaborate with more details? You can add a number of epics or stories to the idea in JPD. But if you want to add a story to an existing epic, you would have to do that from Jira.

[Shawn_Giese]

Exactly, I wanted to push ideas into an existing Epic. As it is now... I push one idea as an epic, then I push remaining ideas as stories. Then I log into Jira and manually pull the stories into the epic. 

I had not realized that Product Discovery did not support hierarchies and so it is not possible to push a group of ideas together (like an epic with assigned tasks).

[Adam Wencel]

I may have this on my radar eventually @Shawn_Giese .  Can you provide a few visual examples of this?  Either from the platform itself or something scratched in notepad.

I want to understand if this aligns with something I'm doing soon.

[Shawn_Giese]

I just made a quick demo. I was hoping to push a parent / child like relationship for work (so I could plan everything in Product Discovery). Without hierarchy, I push each idea out to Jira and then log in to Jira to assemble the pieces.

I thought that maybe "Add a delivery ticket" could at least allow me to target the Epic to add work, but it only adds a link back to the idea, not an actual work ticket.