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

Issue search and bulk move from very large project

Jessica_Moszkowicz

As part of a migration effort from another bug tracking service, we have a single project that currently has around 25,000 issues in it. We would like to start bulk moving some of these issues into other projects. To find the issues we want to move, we will have to do a search on a custom field of type text field. Is this going to be a problem? Is there a limit to how many issues we can have in a single project? What kind of performance can we expect searching and performing bulk operations over 25k issues?

Accepted answers

Jessica_Moszkowicz

As it turns out, there is an open issue that prevents On Demand users from doing bulk edits on more than 300 issues at a time: https://jira.atlassian.com/browse/JRA-32546. It seems like you can attempt to do more than 300, but the request will time out, though it may continue in the background. Unfortunately, there's no way to limit the number of issues returned in a search to 300 other than attempting some sneaky date restrictions.

In the end, we decided not to attempt to bulk move all of our issues, particularly given JRA-32546. We did move a few batches of them successfully though and search was never a problem.

All comments

Mehmet Kazgan_qriny9

Hi Jessica,

That should not be an issue. If you have proper server hardware and settings, that should work fine. I have dealt with up to 15,000 via migration and have not seen an issue with search and indexing.

Here are really good URL's to take a look, which should take care of your concerns:

JIRA Performance Tuning

Making JIRA Survive the Load

JIRA Performance after 300,000 Issues

Jessica_Moszkowicz

We are using JIRA On Demand. Does that change your answer at all?

Andris Grinbergs

Search will not be problem.

Issue count in single project is not a problem also.

But I guess there is 1000 issue limit for bulk changes by default. So if it is one time issue - just move them in 25 turns.

Keep in mind - if you are moving issues between jira projects - issue ID/issue number will change.

Mehmet Kazgan_qriny9

Then you should be covered pretty well, performance tuning with Atlassian is handled really good already.

Jessica_Moszkowicz

In the end, we decided not to attempt to bulk move all of our issues, particularly given JRA-32546. We did move a few batches of them successfully though and search was never a problem.

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