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

How can I migrate issues from one project to another?

Natalia Mojica

Hello!

I'm trying to migrate some issues from one project to another, but I'm having trouble with these fields: Due Date, Delivery Lead, Assignee, and Story Points. When I migrate the issues, the data in those fields is not copied and remains empty.

For this reason I want to know what the possible problem could be and how I can solve it. It seems that the format was different, but I already verified that they are the same fields and the same people

Accepted answers

Ste Wright

Hi @Natalia Mojica

Are you moving the issues from one Project to another, or cloning them?

And what Project types are the source and destination Project (Software or Work Management? Team-managed or Company-managed)?

---

There are possible reasons for this via Move Issues in Company-managed:

Due Date: Ensure you have the "Schedule Issues" permission
Assignee: Make sure the user in this field has the permission "Assignable User"
Story Points: Ensure the field is available for the target Issue Type - it would be limited based on the field context
Delivery Lead: Similar to Story Points, ensure the field is available for the target Project - it would be limited bia the field context

Ste

All comments

Ste Wright

Hi @Natalia Mojica

Are you moving the issues from one Project to another, or cloning them?

And what Project types are the source and destination Project (Software or Work Management? Team-managed or Company-managed)?

---

There are possible reasons for this via Move Issues in Company-managed:

Due Date: Ensure you have the "Schedule Issues" permission
Assignee: Make sure the user in this field has the permission "Assignable User"
Story Points: Ensure the field is available for the target Issue Type - it would be limited based on the field context
Delivery Lead: Similar to Story Points, ensure the field is available for the target Project - it would be limited bia the field context

Ste

Natalia Mojica

Hi @Ste Wright thank you for your answer, I have some questions:

1. How can I see the "Schedule Issues" permission?

2. How the permission "Assignable User" works?

3. For the story points and Delivery lead I'm using the same fields in both projects, so I don't understand what's happening.

I just want to mention that I'm migrating the issues from a team managed project to a company managed project.

Ste Wright

Hi @Natalia Mojica

You can check how Permissions are setup as a Project Admin (although you'll need to be a Product Admin to modify them)...

Go to Project Settings
Select Permissions from the left-hand menu

Assigned users to Project Roles is also possible to view/edit from Project Settings...

Select People from the left-hand menu

---

Other possible issues:

Custom Fields: Are the fields on the Team-managed Project uniquely created, or are they a shared field from the Company-managed field list? If they're uniquely created, the fields might have the same name, but they're still 2 separate fields - and the data will be removed when you move between the 2 Projects. Prior to confirming the move, the confirmation screen will tell you what fields will have their data removed.
Story Points: Similar to the above, the Story Points field in Team-managed Projects is "Story Points Estimate", which is not the same field in Company-managed Projects.

I'd also check out this help page, which details this process and potential additional steps you'll need to take.

---

Story Points - Workaround:

For Story Points, there is a workaround using Automation, where you can duplicate the data from the "Story Points Estimate" field into Story Points

You will need the custom field ID for "Story Points Estimate" before you start:

Go to Settings > Issues
Select Custom Fields from the left-hand menu
Search for "Story Points Estimate"
Select the breadcrumbs (3-dots icon) on the right-hand side, and select "View Field Information"
The ID is in the URL - eg. customFieldId=10006

Next, create the rule as follows:

Trigger: Issue Moved
- Source = Team-managed Project
- Target = Company-managed Project
Condition: Advanced Compare Condition
- First Value = {{issue.customfield_10006}}
- Condition = does not equal
- Second Value = Empty - leave the field empty
Action: Edit Issue
- Field = Story Points
  - Value = {issue.customfield_10006}}

---

Custom Field - Workaround:

You could either...

Add the shared field to the Team-managed Project, then duplicate the data across into it (either via CSV Import or Automation). The data should then remain stagnant during the move. You might benefit from changing the name of one of the fields temporarily to make it easier to differentiate them.
Attempt a similar Automation Rule to the above, to copy the data during the move - although I've not tried this, and as the data is removed in the "move" itself, I'm unsure if this will work

---

Let us know if any of this helps you!

Ste

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-service-management-cloud

jira-service-management