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

For a new project, it gets all versions history event when released

Carolina SILVA

hi community

when I create a new project, due to dataloading we put in place, it gets all versions even released ones!
The impact is that we reached 129 releases, and for the last new project, the project admin was obliged to set released all the former ones.

Any clue to solve that?

Accepted answers

Gor Greyan

Hi @Carolina SILVA

Thanks for the question.

I think this happens because versions are linked to issues. When you create a new project, Jira brings over all versions that are associated with those issues — even old/released ones.

So if your issues were linked to historical versions, those versions will appear in the new project as well. Jira doesn’t automatically filter them out, so you’ll need to clean them up afterward.

All comments

Gor Greyan

Hi @Carolina SILVA

Thanks for the question.

I think this happens because versions are linked to issues. When you create a new project, Jira brings over all versions that are associated with those issues — even old/released ones.

So if your issues were linked to historical versions, those versions will appear in the new project as well. Jira doesn’t automatically filter them out, so you’ll need to clean them up afterward.

Carolina SILVA

Hello @Gor Greyan
thanks for your reply.

I'm not sure it's answers my question.

When I create a new projet, there is no Jira yet in it. So It can't bring versions associated to any issues!

Gor Greyan

Hi @Carolina SILVA

Thanks for the clarification.
In that case, this isn’t coming from Jira itself, but from your data loading process. Jira does not automatically copy versions into new projects, so if all versions (including released ones) appear, they are being created or synced during your data load ( via API, script).

To fix this, you’ll need to adjust the data loading logic to only create the relevant versions for each project, or skip already released ones; otherwise, every new project will continue to receive the full version history.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud