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 move a board from an existing project to a new project?

Pinaki Lahiri

the problem statement is that a new product needs to be created for the work that needs to be accomplished.

How can I move a board from an existing project to a new project? the number of Epics and tasks in the existing board will take a lot of time to recreate on the new project. Hence looking for a way to move the entire board to the new project.

Accepted answers

Trudy P Claspill

Hello @Pinaki Lahiri

Welcome to the community.

First let us clear up terminology.

Issues are contained in Jira Projects.

Boards are a way to visualize and manipulate issues. Boards are based on filters that select issues. The filter can select the issues based a variety of criteria including which project the issues is in or other factors like the values contained in fields.

If I understand correctly you already have Epics and Issues defined in a project, and they are being displayed in a board.

Now, I have a few questions.

1. Do you want a copy of those issues in a new project, to start working on them from scratch? Or do you want to remove the issues from their current project, and move them with all their history to the new project?

2. Do the issues exist in a Company Managed project or a Team Managed project? When you are viewing the project, at the bottom of the navigation pane on the left it will say either Company Managed or Team Managed.

3. Is this a Software project, a Service project, or a Business project? That will be shown below the project name at the top of the navigation pane on the left.

4. What type of board are you using; Kanban or Scrum?

All comments

Trudy P Claspill

Hello @Pinaki Lahiri

Welcome to the community.

First let us clear up terminology.

Issues are contained in Jira Projects.

If I understand correctly you already have Epics and Issues defined in a project, and they are being displayed in a board.

Now, I have a few questions.

3. Is this a Software project, a Service project, or a Business project? That will be shown below the project name at the top of the navigation pane on the left.

4. What type of board are you using; Kanban or Scrum?

Pinaki Lahiri

Hello Trudy how are you?

Lets us start from point 4

4. It is a Scrum Board

3. Software Project, application

2. Team Managed Project

1. I understand that when you create Epics and Issues, its picks up the project key. Now I am not aware if the entire board can be moved/copied to the new project? what happens to the product/project key?

Trudy P Claspill

Hello @Pinaki Lahiri

With a Team Managed project, a board is created automatically and its filter is set to select all issues in the project. You can't "move" a board from one Team Managed project to another project.

You can move the issues from one project to another project. When you more an issue its issue key will change to include the project key of the new project.

Let us say you have a project:

name: Team Managed Project A

project key: TMPA

When you create issues in that project the issue keys are set to TMPA-###.

Let us say you have a second project:

name: Second Project

project key: SP

If you move an issue from the TMPA project to the SP project then the key for that issue will change from TMPA-<someNumber> to SP-<aDifferentNumber>.

Also, when you move that issue, that issue will no longer be displayed on the board associated with the TMPA project.

You can move all the issues in your project to a different project. The issue keys for all the projects will change. The issues will no longer be visible in the Board for the original project.

You cannot move the board associated with a Team Managed project to another project. You will have a new board for that other project where the board has either been created automatically (as is done for Team Managed projects) or a board you create manually.

Note that due to the customizations in Team Managed projects being project specific, if you do choose to move issues to another project then you will lose the data in custom fields that you have added.

Perhaps if you provide the details of the problem you are trying to solve I'll be able to provide better guidance.

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-software

jira-software-cloud

atl-gruland