Migrating a JSM Project when JSM is not installed in Target Instance

Problem

Below is the error message you see when the Jira Service Management application is not installed in Target Instance 

• The above "Missing plugins" error is shown because the snapshot contains configuration objects of types that are contributed by these plugins, and deploying the snapshot without them can result in data loss.
• In this case, Jira Service Management, which constitutes a bunch of plugins for the different parts of the functionality, contributes custom field types, some post functions, etc.
• When these objects are included in the snapshot, because they are part of the configuration of the selected project(s) (assuming a project or project with issues snapshot), CMJ detects that their types are contributed by those apps and requires them on deployment in order to prevent any data loss or integrity violations.

Solution

Follow the below approaches to migrate and overcome the issue:

Approach 1

• CMJ's Power Admin can be used to inspect configuration objects contributed by JSM and how they are referenced by the projects that need to be moved, then, the configuration can be changed to remove these references based on the documentation here.

• Currently, Power Admin does not support JSM-specific configuration, i.e. configuration that is part of a service desk project, but it will show all items like schemes, screens, workflows, etc. that refer to the problematic objects.
  
  

  We recommend this be tested on a staging instance if the changes are not desired on the source instance.

Approach 2

• Alternatively, JSM can be installed on the target Jira instance before performing the deployment and can be removed after that.
• Some unnecessary configuration items may be left after the removal of JSM, but they should be easy to find with Power admin and then removed.
• A trial license should suffice for the temporary installation of JSM, and the deployment should work even if JSM isn't licensed.