Moving projects from JSM managed spaces to JIRA managed space

[Harshveer Kaur]

Hi team,

we have few spaces which are managed under JSM (Screenshot attached).

We want to move then under JIRA managed spaces (Sample screenshot attached).

We have to move all the work items from JSM to JIRA be it open, resolved or closed.

How can we move all these spaces from JSM to JIRA minimising the manual work.

[Trudy Claspill]

Hello @Harshveer Kaur 

Do you want to retain all the fields and data? Note that JSM specific fields and data will not be retained including but not limited to Request type, SLAs, CSAT.

Is the source Space Team-managed or Company-managed? That info can be obtained from the Type column on the View All Spaces page, or by clicking the ... button next to the space name and reviewing the last two lines of the pop up.

How many items are in each source Space?

Here is a summary of what you would need to do.

1. Create the destination Space as a Software space. I recommend that you choose a Company-managed Software space.

2. During that creation process, if the Source space is Company-managed then you can elect to have the new Space Share Configuration with the source Space. The new space will then use the same workflows, work item types, screens, fields, etc. as the JSM Space.

3. Use the Filter > Search Work Items screen to retrieve all the items in the source Space.

4. Use the Bulk Change feature and the Move operation therein to move the items from the JSM Space to the new Software space. I recommend you test first by moving some cloned issues to ensure they move as expected and no unexpected data loss occurs.

Note that when you move the items your Customers will no longer be able to see them in the Customer Portal. And the item keys will change.

If the source or destination spaces are Team-managed then the process is more complicated.

[John Funk]

Hey @Trudy Claspill I don't think step 2 is correct. If you create a Jira Software space and use a JSM space as the shared space, it will create the new space as a JSM space based on the one you selected, and not a software space as you are intending. 

[Trudy Claspill]

@John Funk 

You are correct!!

I just tried it, and that path does indeed create the new project as a Service type project. My apologies to @Harshveer Kaur for providing an incorrect answer.

It would, perhaps, work to instead complete the creation of a new generic Software project without using the Share Configuration option. Then modify which configurations are associated with the project so that it uses the configuration schemes used by the source Service project.