JPD Space Ideas Limit (5000 ideas per space)

[Apoorv Sahai]

Hi everyone,

We're migrating our product team from CODA to JPD and have realized that our ideas will definitely exceed the 5k limit.

-Can you confirm if archival frees up space?
-Can you suggest alternate ways to handle projects where the ideas exceed the 5k limit.

[Tomislav Tobijas · Accepted solution]

Hi @Apoorv Sahai ,

I'm going to move this to the JPD Q&A section so someone from JPD product team might chime in.

Based on the official limitation stated here and how Jira generally works, archived ideas are still counted towards that limit 👀

I guess the option would be to split ideas you have into multiple projects/spaces (probably the most effective workaround at the moment). You can organize these projects by product line, specific teams, or strategic themes... (as I guess perma-deletion is not an option 😅)

On JPD Premium you also have multi-space Roadmaps with which you can then visualize all these cross-space ideas.

Anyway, I hope someone from JPD team will jump in to confirm (or correct) what I just said.

Cheers,
Tobi

[Apoorv Sahai]

Thanks Tobi! Makes sense
Would be glad if you could move this to the JPD Q&A section.

[Marc -Devoteam- · Accepted solution]

Hi @Apoorv Sahai 

Welcome to the community.

The liie of 5K of Ideas is per JPD space and can't be extended.

Archiving to another space will help, but archiving in a same space, not as this will still count to the limit, as the work item is still in the same space.

"5,000-idea limit is a total project storage limit that counts both active and archived ideas. Archiving only clears up your insights count"

[Apoorv Sahai]

Thanks Marc, this is pretty helpful!

[Gor Greyan · Accepted solution]

Hi @Apoorv Sahai

Welcome to the Atlassian Community!

The 5,000 ideas per JPD space is a product limit, so if you already know your migration will exceed that number, I wouldn’t recommend designing the solution around a single space. The better approach is to split the ideas into multiple JPD spaces based on a meaningful boundary — for example, product, product area, business unit, or team. This also tends to make views, permissions, and discovery work easier to manage as the dataset grows.

Atlassian also recommends considering multiple spaces when dealing with a large number of ideas.