JCMA throws `Illegal Argument Exception:You have to provide a value mapped string` on migration of notification schemes containing unsupported notification types

XMLWordPrintable

    • 7
    • Minor
    • 2

      Issue Summary

      JCMA throws `Illegal Argument Exception: You have to provide a value mapped string` on the migration of notification schemes containing unsupported notification types

      Steps to Reproduce

      1. Download the app from here - https://bitbucket.org/davfive/jira-parent-watcher/downloads/
        • Note- This error could occur for another app also - currently unknown
      2. Upload this app to Jira Server by going to Manage Apps -> Upload App
      3. Go to the default notification scheme
      4. Add notification Parent Watcher to any of the system events apart from Issue Archived and Issue Restored 
      5. Create a project, by default, it would be associated with this scheme
      6. Migrate this project via JCMA

      Expected Results

      Successful migration of notification schemes without any error.

      Actual Results

      The below exception is thrown in the atlassian.jira.log file:

      Exporting entity Notification Scheme 10000 failed 2java.lang.IllegalArgumentException: You have to provide a valid mapped string 3 at com.atlassian.jira.notification.type.NotificationType.from(NotificationType.java:54) 4 at com.atlassian.jira.migration.export.core.project.NotificationSchemeExporter.isSupportedNotification(NotificationSchemeExporter.kt:94) 5 at com.atlassian.jira.migration.export.core.project.NotificationSchemeExporter.mapEvents(NotificationSchemeExporter.kt:66) 6 at com.atlassian.jira.migration.export.core.project.NotificationSchemeExporter.exportData(NotificationSchemeExporter.kt:54) 7 at com.atlassian.jira.migration.export.core.project.NotificationSchemeExporter.exportData(NotificationSchemeExporter.kt:30) 8 at com.atlassian.jira.migration.export.framework.ExportService$exportJiraEntity$1$1.invoke(ExportService.kt:291) 9 at com.atlassian.jira.migration.export.framework.ExportService$exportJiraEntity$1$1.invoke(ExportService.kt:290) 10 at com.atlassian.jira.migration.metrics.TimingMetrics.time(TimingMetrics.kt:22) 11 at com.atlassian.jira.migration.export.framework.ExportService.exportJiraEntity-0E7RQCE(ExportService.kt:290) 12 at com.atlassian.jira.migration.export.framework.ExportService.exportByEntityImpl(ExportService.kt:234) 13 at com.atlassian.jira.migration.export.framework.ExportService.exportByEntityImpl$default(ExportService.kt:213) 14 at com.atlassian.jira.migration.export.framework.ExportService.exportOrNull(ExportService.kt:339) 15 at com.atlassian.jira.migration.export.core.project.ProjectExporter.mapNotificationSchemeOrDefault(ProjectExporter.kt:343) 16 at com.atlassian.jira.migration.export.core.project.ProjectExporter.exportData(ProjectExporter.kt:143) 17 at com.atlassian.jira.migration.export.core.project.ProjectExporter.exportData(ProjectExporter.kt:72) 18

      Workaround

      1. If easily identifiable, remove the custom notification type from the notification schemes associated with the projects you're migrating.
      2. Otherwise, open a ticket with the Cloud Migrations Support team and provide the output of the following SQL query in a CSV file: 
        SELECT DISTINCT NOTIF_TYPE FROM NOTIFICATION;

        Public facing article: https://confluence.atlassian.com/cloudkb/java-lang-illegalargumentexception-you-have-to-provide-a-valid-mapped-string-error-when-running-a-migration-plan-in-jcma-1129682631.html

            Assignee:
            Unassigned
            Reporter:
            Vaibhav Agarwal
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: