Migrating from Company to Team project: the "Done" items

[Steve H_]

Afternoon:

I'm in the process of migrating a Doc Req ticket system project I built from a Company-managed Software project to a Team-managed Business project.

I currently have a Kanban board with the following fields representing the Doc Life Cycle process:

• Backlog
• Prioritized
• Build
• Production ready
• Done

If I read the documentation correctly, the "My Open Issues" (associated with me) will be migrated to the new project. What I don't see is what will happen to the "Done" column of Doc Req tickets--which I also want to bring over.

Will the Migration process also bring the across the completed tickets (issues)?

I really don't want to have them disappear in the migration process.

Thanks and Happy New Year.

[Trudy Claspill]

Hello @Steve H_ 

What documentation are you referencing? Can you provide the link?

Where are you getting the idea that only "My Open Issues" will be migrated?

What functionality are you using to migrate the issues? Are you using the Move Issue function?

Note that in Business projects Done issues will automatically be hidden after 2 weeks with no updates.

A Company Managed Kanban board lets you configure that time period or turn of hiding done issues entirely, and also looks at the Resolved date when making that decision.

A Team Managed Business project does not let you configure the time period or turn off hiding done issues, and it looks at the Updated date. Business project do not set either the Resolved date field or the Resolution field.

If you use the Move Issue function, the issue will indeed be moved to the new project. The Move process with also cause the Updated date/timestamp to be updated, so Done issues will display in the Done column immediately after the move.

Do be aware that Business projects have a limit of displaying only up to 1000 issues on their boards. If you are moving more than 1000 issues, or expect to have more than 1000 active issues at times, you will see the oldest of those 1000 issues.

https://jira.atlassian.com/browse/JWMCLOUD-23

[Steve H_]

Reference link:

https://support.atlassian.com/jira-service-management-cloud/docs/migrate-between-next-gen-and-classic-projects/

One of the subsections references moving existing issues. That seemed to imply that those were current issues instead of closed issues.

[Trudy Claspill]

I'm not finding anything in that document that implies only not-done issues will be moved. If you want to explore that more, to correct terminology misunderstandings, please paste the exact text that gave you that impression.

[Ste Wright]

Hi @Steve H_ 

What document are you referring to? Is it this document here?

Assuming you're following these instructions, you can choose to migrate all your issues - not just the open ones.

See this part here:

Search for your existing issues

First, you need to find the issues you want to move:

1. Select the search field in the navigation bar and select View all issues.

2. Click the Project filter, and select the project you want to migrate from.
   (If you're looking at the Advanced mode, you'll need to select Basic)

3. In the top-right corner, select more () > Bulk change all. The Bulk Operation wizard appears.

^ You can choose to "view all issues" and move them, open or not :)

Ste

[Steve H_]

okay, thanks; I'm seeing I'll need to also recreate my custom fields (and I have mostly custom) within the new project.

Thanks for the prompt response.

[Ste Wright]

No problem! Let us know how it goes!

Ste