Jira Bulk Move: A Step-by-Step Guide to Safely Moving Issues
Moving Jira issues across projects? This Jira bulk move guide helps you avoid key and field problems. Read now to move safely.
Jira bulk move lets you transfer several issues between projects in one operation. Done carefully, it saves time when a team reorganizes work or closes an old project. Done hastily, it can leave issues with incorrect types, statuses, components, or ownership.
A move can also change issue keys, affecting links people have bookmarked or connections with other systems. That makes a quick selection and a single click riskier than they first appear.
But here's the truth: a safe move depends more on preparation and verification than on the bulk action itself. You need to check permissions, map destination fields, and test a small group before moving everything.
In this guide, I’ll walk you through the Jira steps, the checks to make before and after moving issues, and ways to handle common problems. You’ll finish with a practical plan for moving work without avoidable surprises.
How to Bulk Move Jira Issues Safely
Use Jira’s bulk change workflow to select issues, choose a destination project, map incompatible fields, and review the results. Start with a small test group, then repeat the process for the remaining issues.

1. Confirm access and plan the move
Before selecting issues, confirm that your Jira account can access both projects and perform bulk changes. You’ll generally need the global Bulk Change permission, plus the relevant project permissions for browsing and moving issues.
Ask a Jira administrator to check permissions if the bulk option is missing or Jira blocks the operation. Also agree on the destination project, the issues to move, and a time when affected teammates can avoid editing them.
2. Identify and review the issues
Open Jira’s issue search and filter for the issues you want to move. Narrow the results by project, issue type, status, assignee, or another useful field, then inspect the results before selecting anything.
For example, a team moving 40 open support tickets might exclude resolved tickets and confirm that each selected issue belongs to the intended project. Check parent and subtask relationships, linked issues, and any issues with special security settings.
3. Start the bulk move
Select the intended issues in the search results. Choose the bulk change action, select the move operation, and follow Jira’s prompts. The labels and exact screens can vary between Jira editions and interface versions.
Read each confirmation screen carefully. If Jira shows a count of selected issues, compare it with your expected total before continuing. Cancel if the count or destination looks wrong.
4. Map issue types and destination fields
Choose the destination project and map each current issue type to a compatible type there. For example, a source project’s “Defect” type might need to map to the destination’s “Bug” type.
Jira may also ask you to map statuses or provide required destination fields. Review components, versions, assignees, security settings, and custom fields. Resolve validation errors before proceeding instead of choosing values at random.
5. Test, complete, and verify
Move a small, representative group first. Include different issue types and statuses if the larger group contains them. Then inspect the moved issues for correct fields, workflow status, comments, attachments, links, and parent-child relationships.
If the test looks right, repeat the operation for the remaining issues. Afterward, compare the moved issue count with your plan, check a sample of records, and tell affected teammates what changed.
Prepare the Destination Before Moving Issues
Successful moves begin with a destination project that can accept the incoming work. Compare its issue types, workflows, required fields, components, versions, and permissions with the project you’re leaving.
Here's why: Jira may require a value that the old project never used. If the destination requires a component, for example, issues without one may fail validation or need a deliberate default.
Consider a team moving bugs into a product project that uses a different status workflow. Agree on how “In Review” maps to the destination workflow before the bulk operation begins. A clear mapping prevents inconsistent status choices across batches.
Understand Issue Keys, Links, and Relationships
Moving an issue to another Jira project can change its issue key because the key includes the project identifier. A ticket such as HELP-245 might become APP-812 after the move.
Jira may continue to recognize the old key in some contexts, but don’t assume every bookmark, report, or connected system will handle the change the same way. Check saved filters, dashboards, automation rules, and integrations that refer to affected issues.
Let me explain: an issue can move successfully while a team’s reporting still points to the previous project. For example, a dashboard filtered to project = HELP won’t necessarily show issues now assigned to APP.
Run a Small Test and Verify the Results
A test move helps reveal mapping problems before they affect a large group. Choose a handful of issues that represent the different types, statuses, and field combinations in the full set.
Check the test issues in the destination project. Confirm that required fields have sensible values, workflow statuses make sense, and people can still access the issues. Review comments, attachments, links, and subtasks where relevant.
The best part? You can use what you learn to adjust the full move. If Jira rejects an issue because a field is required, fix the mapping or prepare that field before moving the remaining group.
Communicate the Change and Update Team Processes
Tell teammates when the move will happen, which projects are involved, and whether issue keys may change. Share the destination project and explain where the team should look for moved work.
After the move, update team filters, reports, automation, and internal references that depend on the old project. A short checklist can keep these follow-up tasks visible, especially when more than one team relies on the affected issues.
For instance, a product team might update its sprint filter and alert rules after support tickets move into its project. That prevents moved issues from disappearing from daily views or triggering outdated notifications.
Value proposition: ONES.com combines project management and knowledge management in one platform, with ONES Project for project work and ONES Wiki for team knowledge. The products are sold separately, so you can choose the capability that fits your needs.

If you’re evaluating a Jira alternative while reorganizing projects, ONES Project provides Jira-compatible workflows and project management features. A platform change still needs its own migration plan; issue fields, workflows, and team habits should be reviewed before moving work.
Core capabilities
- Pain: Teams rely on many add-ons for everyday project work. ONES capability: ONES Project includes sprint management, automation, and built-in reporting. Result: You can handle common planning and tracking needs with fewer plugins.
- Pain: A standard workflow doesn’t match how your team handles work. ONES capability: Configure custom workflows and fields. Result: The project process can reflect your team’s actual stages and information needs.
- Pain: Teams want a familiar project process when considering a Jira alternative. ONES capability: Jira-compatible workflows support familiar patterns. Result: Teams can evaluate a different platform without discarding every established workflow concept.
- Pain: Project status is difficult to understand across teams. ONES capability: Built-in reporting gives teams project visibility. Result: People can review progress without assembling every update manually.
- Pain: A company needs to keep project information within its environment. ONES capability: Deployments include Cloud, On-Premise, Private Cloud, and Air-gapped options. Result: Teams can choose an environment suited to their operating requirements.
- Pain: Self-hosted teams worry about losing capabilities available in the cloud. ONES capability: The self-hosted version has full feature parity with the cloud version. Result: Deployment choice does not require accepting a reduced feature set.
- Pain: Teams want to connect project work with shared knowledge. ONES capability: ONES.com also offers ONES Wiki, a knowledge base product. Result: Teams can consider project and knowledge management within one platform while selecting the products separately.
- Pain: A team wants to test project management before making a broader commitment. ONES capability: The free plan supports up to 30 seats. Result: A team can evaluate its project workflow with a small group.
Application scenarios
Project teams replacing or reassessing Jira: A team can review ONES Project’s workflows, fields, sprint management, and reporting against its current process. It should map its needs and test representative work before choosing a migration approach.
Organizations with restricted environments: A company that needs self-hosting can evaluate On-Premise, Private Cloud, or Air-gapped deployment. Teams can also assess ONES Wiki separately if they want a dedicated knowledge base alongside project management.
Common Challenges When Moving Issues
- Bulk change is unavailable. Check with a Jira administrator about global bulk permissions and project-level access. Confirm that you’re using the expected issue search view and that the selected issues are eligible for the operation.
- Jira reports field or workflow errors. Compare destination requirements with the selected issues. Map issue types and statuses deliberately, and supply required values before restarting the move.
- Some issues are missing from the results. Review the search filter, project permissions, and issue security settings. Check that the query includes the intended statuses and issue types before selecting the results again.
- Reports or integrations still refer to old project details. Review filters, dashboards, automation, notifications, and connected systems after the move. Update project references and test key views with a moved issue.
FAQs About Moving Jira Issues in Bulk
Does moving a Jira issue change its issue key?
It can. Jira issue keys include a project identifier, so moving an issue to another project can give it a key associated with the destination. Check the resulting keys after a test move, especially if people rely on bookmarks, reports, or integrations. Share the new project location with teammates and update references that depend on the old project key.
Can I move issues with different issue types together?
You may be able to select different issue types in one bulk operation, but each type needs a valid destination mapping. For example, map “Defect” and “Task” to the appropriate types in the destination project. If the destination lacks a matching type, check with your Jira administrator before proceeding. A small test can reveal mapping or validation problems early.
Will comments, attachments, and links remain after a move?
Review these details during a test move rather than assuming every relationship behaves as expected in your Jira edition and setup. Inspect comments, attachments, issue links, and parent-child relationships on representative issues. Also check whether integrations or reports recognize the moved issues. If any critical relationship is missing or behaves differently, pause before moving the rest.
Can I undo a Jira bulk move?
Don’t treat a bulk move as a simple action that can always be reversed with one click. Jira’s available options can depend on your setup, permissions, and the changes made after the move. Before proceeding, record the selected issues and intended mappings, and agree on a recovery plan with your Jira administrator. Test the operation first and verify the outcome before moving a larger group.
Conclusion
Jira bulk move can save time when projects change, but careful preparation protects issue details and team workflows. Check access, review the selected issues, map destination fields, and test a representative group before moving the rest.
Then verify issue keys, relationships, reports, and integrations, and tell teammates where to find the moved work. With a clear plan and a careful review, you can move Jira issues with fewer surprises and keep work visible to the people who need it.