Configuration Manager for JIRA vs Project Configurator for JIRA

[KRC]

HI

Which addon is more efficient to use for migrating projects from one instance to other?

Which add on can or will migrate comments, attachments, and entire activity section from instance to instance?

By using these add on's do we need to manually create all custom fields, screen, issuetypes in other instance before migrating?

Any known limitations?

Which way is good, either using plug in for migration or match version of both instances and back up projects needed to migrate and restore it in other instance?

[Nic Brough -Adaptavist-]

Both of them are good, and I can't say which one is "more efficient" because it depends on what you're doing and why.

Both of them enable migration of everything.  The whole point they exist is to take across the screens, fields, issue types and so-on.

Limitations are that they do not handle some third party custom fields.

You won't need to restore anythign, the add-ons handle almost everything (Botron makes the system ready to do a "project import", PC can take the issues itself)

[Theo Gravity]

Wanted to add that Configuration Manager does not support migrating JWT:

"

Unfortunately, JWT currently isn’t supported by Configuration Manager for Jira, thus causing some post function properties to not have correct values, as they are deployed as-is on the target instance. Currently we support a few 3rd party apps, the full list is available here - https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784154/Support+for+Apps

We recently released a way for other developers to extend CMJ with their app’s custom configurations - https://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/622755882/Service+Provider+Interface+SPI

We are working with Decadis AG to implement this integration. It will help if you also give this feedback to them too, so they are aware of the users that need to be able to migrate this kind of configuration.

"