"java.lang.IllegalArgumentException: You have to provide a valid mapped string." error when running a migration plan in JCMA
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem summary
When running a migration plan with JCMA, it may fail with the error below (JCMA logs):
2022-05-17 11:46:11.568 ERROR INTERNAL project-export We couldn't export Notification Scheme <notification scheme ID>. Reason: java.lang.IllegalArgumentException: You have to provide a valid mapped string.Affected products
- Jira Server/DC (any version compatible with JCMA → 7.6.0 and higher)
- JCMA 1.6.9 (Notification Schemes migration is supported by JCMA as of this version)
Why?
- This error has popped up in Jira Server/DC instances that have an app named Jira Parent Watcher installed.
- This app is not present in the Atlassian Marketplace and was supported back in Jira 6, in 2012. It's an old app.
- The issue surfaced because this app offers a custom notification type named Parent Watchers which is not supported by JCMA.
Solution
If you're affected by this, it'd mean you're affected by this bug: MIG-1056 - JCMA throws `Illegal Argument Exception:You have to provide a value mapped string` on migration of notification schemes containing unsupported notification types
The workaround is to remove this custom notification type from the notification scheme associated with the projects being migrated.
Otherwise, it may fail with the error above.
This error may surface for different third-party apps as well.
So if you see this specific error message in JCMA logs, check if you have third-party notification types in the notification scheme associated with the affected project.
SQL check
If you're unable to identify the custom notification type, don't hesitate to open a ticket with Cloud Migrations Support to help you address this issue.
When opening the ticket, make sure to attach the following:
- JCMA logs (from JCMA dashboard, View Details dropdown menu on the failed plan)
- A Support zip file from your Jira instance
The output of the SQL query below in a CSV file
SELECT * FROM notification;
Reference links
- Configuring email notifications
- Creating a notification scheme
- Use the Jira Cloud Migration Assistant to migrate