Setting up & migrating Jira projects

Notify people when you are planning to migrate their projects unless you are doing it off hours.

Ensure that the team working on the project has the appropriate licensing assigned to them by adding them to the appropriate AD group. We should be covered in most cases because I believe Dan added ir-everyone to software, work-management, confluence, and Jira-service-management but double check.

All of these groups are under Atlassian OU in AD

• Jira-software-license

• Jira-work-management-license

• Jira-service-management-agent-license

• Jira-service-management-customer-license

The only projects that we are going to keep in the cloud as Software are actual SW development projects, all others should eventually move to Jira Workflow Management projects.

Check to see if there are automation rules that have been set up for the project as those will likely need to be reimplemented.

Migrate the project - migrations will be Jira Software to Jira Software or JSM to JSM

Create a migration

Advanced Roadmaps -choose none

Projects - Choose your project and choose All

Users and groups - None

Customers - Only users and group related to the selected project, include … assigned to required roles

Group - preserve group membership

Apps - none

Once migrated, append delete to the end of the project name (so that you can create a new JWM project with the same name). This only applies to Software projects that we are migrating to JWM.

Create a new JWM project

Projects should be created as Company managed

Project Settings

Issue Types

Actions

Use a Different Scheme

Use the Default Project Management Issue Type Scheme

Workflows

Switch Scheme

Use the Default Project Management Workflow Scheme

Associate

Assign an appropriate category for the project - LTS in most cases

Assign the appropriate people to roles in the People section of the project.

• Remove anything there by default

• The jira-lts group should be given the Read Only role for LTS projects

• Appropriate project lead should be assigned and then you will let them know that they should assign the appropriate people to the Team role for that project now that they have the permissions to do so.

Go into the original migrated project, select all issues, bulk change, and move to the new JWM project you just created.

Check boards and filters associated with the project to make sure that the ownership is assigned to the appropriate people. For some reason the filters get associated with the person doing the migration so those permissions will need to be adjusted in order for the boards to work.

Verify that everything moved correctly and then delete the original project that you migrated over

Project lead should manage assigning the appropriate people to the Project Team role that will allow them to work on individual projects. Notify the project lead of that responsibility when communicating in the migration request ticket.

Once the project lead gives the go ahead the migrated project looks good, update the permission scheme for the project to not allow create. Perhaps rename the project on jira.cc.lehigh.edu to add in “migrated” to the title and change the permission scheme to “Archived”.