JCMA should help to resolve entities that are deleted already

XMLWordPrintable

    • 2
    • Hide

      Currently, JCMA's pre migration checks will not identify the custom fields that are associated with deleted users or groups. In order to fix these, one must find the IDs after migration has been performed, following the article on How to resolve Automation rules migration errors. However, this is time-consuming and cumbersome to re-migrate projects with the corrected entities.

      JCMA should provide a method for identifying these missing entities, such as deleted groups before the migration. For example, pre migration report should pick these up so that the customer can migrate after the unresolved entities are fixed. This will prevent the need to remove duplicated entities, and/or projects for remigration.

      Show
      Currently, JCMA's pre migration checks will not identify the custom fields that are associated with deleted users or groups. In order to fix these, one must find the IDs after migration has been performed, following the article on How to resolve Automation rules migration errors . However, this is time-consuming and cumbersome to re-migrate projects with the corrected entities. JCMA should provide a method for identifying these missing entities, such as deleted groups before the migration. For example, pre migration report should pick these up so that the customer can migrate after the unresolved entities are fixed. This will prevent the need to remove duplicated entities, and/or projects for remigration.

      Currently, JCMA's pre migration checks will not identify the custom fields that are associated with deleted users or groups. In order to fix these, one must find the IDs after migration has been performed, following the article on How to resolve Automation rules migration errors. However, this is time-consuming and cumbersome to re-migrate projects with the corrected entities.

      JCMA should provide a method for identifying these missing entities, such as deleted groups before the migration. For example, pre migration report should pick these up so that the customer can migrate after the unresolved entities are fixed. This will prevent the need to remove duplicated entities, and/or projects for remigration.

            Assignee:
            Unassigned
            Reporter:
            Jinmo Yi (이진모)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: