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

Moving an idea to another project doesn't auto-redirect

Seth Mason

I had an product discovery idea (idea-1) and needed to move it to a Jira Software Project (company managed). Product Discovery didn't appear to have a "move" function, so I used advanced search, and then 'bulk move' to move it from idea-1 to the Jira Software Project.

I can still access the idea using the original URL:

https://x.atlassian.net/jira/polaris/projects/<discovery project>/ideas/view/123456?selectedIssue=idea-123

(btw, I cannot add comments to it or even archive it). It appears to be a dead end.

Normally, when you move an epic/task etc between projects, and you access the original key, JIRA redirects to you to new key.

Accepted answers

All comments

Tanguy Crusson

Hi @Seth Mason , that's a limitation of the beta currently: we don't really support moving ideas between projects yet. E.g. if you move an idea to another discovery project you'll lose the connection to insights. It's something we definitely plan to support on our way to GA.

James Doyle_bt35kt

HI @Tanguy Crusson do you have any update on when moving ideas between projects will be supported?

I recently started using JPD and had one project per team (of which we had 5). Now we have had a restructure in the business and we have gone to 2 teams and I now need to move ideas from one JPD project to another.

We have lots of ideas to manage and recreating manually is not ideal.

Sorry to piggy back on this post but seemed most relevant rather than starting a new thread.

Regards, James.

Tanguy Crusson

Hi @James Doyle that's coming soon - there's an engineer on the team working on this. After his change you can move ideas without losing insights, using the standard Jira bulk-move functionality.

However remember that Jira Product Discovery is built on top of Team-managed projects, so bulk-move doesn't preserve field values (since every project has a unique set of fields, even if they have the same name). That's one of the things we plan to make easier after we ship the first change.

Michael Schmidt Linneberg

Hi @Tanguy Crusson

Any news on this? We've been playing around with your tool now for a couple of months and love it. But we split our ideas up into two projects and really need to compile them in one project for better comparison. Would love it if it was possible to bulk-move all ideas from one project into another one.

Also, could you elaborate on what field values would persist when moving? Will everything disappear and only the title remain? Or will new fields just be created in the destination project?

Regards,
Michael

Welcome!

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