Jira Agile is required when deploying project(s) with no usages of Jira Agile/Software objects

Symptoms:

When deploying project (or multiple projects) that doesn't contain any Jira Agile/Software objects referenced in its configuration then CMJ reports Jira Agile as required plugin to continue the deployment. The source instance has Jira Agile installed while the target instance has no Jira Agile.

Cause:

The most common reason for CMJ to report a plugin as required during a project deployment is a custom field provided by that plugin referenced by some of the project configuration or with a value in some of the project's issues.

There are two custom fields provided by Jira Agile/Software that CMJ will treat differently if Jira Software is installed on the source instance:

Epic Color

This field will always be included in the snapshot if the snapshot contains issues or the option for including fields with values in issues is selected. Jira will always treat that all issues have value for "Epic Color".

Rank

This field is global and will be included in the snapshot no matter what projects are exported. The field will be used by CMJ to maintain the ranking of the issues if they are part of a board.

Resolution:

To continue the deployment you will need to install Jira Software on the target instance. It is enough to have Jira Software only during the deployment. You can also use a trial license for Jira Software and uninstall it after the deployment if it is not needed on the target instance.