Bulk Copy

Cloud Migration Resources

Planning a Jira Cloud migration? These resources can help you get started:

JSU Cloud features – Review Cloud features and understand key differences between DC and Cloud.
Migration support from Appfire – Learn how we can help you migrate smoothly.

Bulk Copy

This is the documentation of JSU for Jira Data Center. Bulk Copy is available only with our Data Center app. If you are using JSU on Jira Cloud, see our JSU Cloud documentation.

Description

You can copy a set of issues (the current result of an issue filter) to a specified Jira project.

How to bulk copy issues

  1. Prepare a Jira filter. Use Jira's search dialog (issue navigator) to create a filter for the issues you want to copy. Learn more about creating and saving filters in Atlassian's documentation.

  2. Choose the target project. You need the Administer Projects permission for the target project.

  3. In the project administration, select Bulk Copy Issues from the Actions dropdown.

    Bulk Copy Issues shown in the Project Administration Actions dropdown.
  4. Select one or more options to define what will be copied.

    The Bulk Copy Issues options page.
  5. Select Bulk Copy Issues to start the copy process. A progress bar displays.

What happens with issue links between issues?

  • If both issues linked in your search filter (TF-1 → TF-2) are part of the same issue, a corresponding issue link will be created between the copies (XY-1 → XY-2).

  • If there is an issue link pointing to an issue outside of your search filter (TF-1 → TF-3), the issue link from the copied issue will point to the same issue (XY-1 → TF-3).

Example of the issue links described on this page.

This feature applies to issue links. Epic links are not supported with the above functionality. From the copied issue, the epic links will always point to the original epics.

Order of created issues

This affects the issue keys. Principally, the new issues will be created in the same order as in the result of your search filter. However, subtasks will always be created immediately after their parent.

Restrict who can perform bulk copy

You need the Administer Projects permissions in the target project to perform bulk copy. To further restrict this, you can create a user group with the name:

bulkcopy-users

and assign the users you want to allow to perform bulk copy to this group. Then, only these users can perform this action.

If the group 'bulkcopy-users' does not exist, then anyone can perform bulk copy in the projects where they have Administer Projects permission.

Limits configuration

Since JSU 2.7.0:

Bulk Copy can generate a lot of load on your instance. To prevent overload, you can configure the following two limits:

  • Number of issues that can be copied

  • Number of simultaneous Bulk Copy jobs

Number of issues that can be copied

This can be configured through the Jira Application Property

jira.search.views.default.max

The default value is 1,000. To read more about how to configure Jira Application Properties, see Advanced Jira application configuration.

Number of simultaneous Bulk Copy jobs

This can be configured by using the following System Property

-Dch.beecom.jira.jsu.action.bulkcopy.processormanager.maxconcurrentprocessors=<Number of simultaneous Jobs>

The default value is 10 simultaneous Bulk Copy jobs. To learn more about how to configure System Properties in Jira, see Setting properties and options on startup.

Need support? Create a request with our support team.

Copyright © 2005 - 2026 Appfire | All rights reserved.