Projects
Related content
- No related content found
Last modified on Apr 26, 2024
In this section
- "Exporting entity Portal Settings <ID> failed" on service project migration
- "Group name already in use. Please choose another to continue" error when migrating service projects
- "Need a parameter for notification type SINGLE_USER" during project migration
- "There was a problem retrieving your plans" error message
- "We couldn't export Issue Reason: java.lang.NullPointerException" error message in JCMA
- [JCMA 119] Screen Scheme has no screen configured for the default issue operation
- API to Fetch ID Mappings from Jira Cloud Migration Assistant
- Couldn't migrate Request Type with id linked to Issue Type with id
- Exporting entity Issue failed with java.lang.NullPointerException
- Groups contain permissions for products that do not exist on your cloud site
- IllegalArgumentException: Missing mandatory keys in arguments of Validator
- Issue source of type Board, with value [board_id] could not be found
- JCMA doesn't migrate all Custom Fields
- JCMA doesn't migrate issue security level permission with unsupported custom fields
- JCMA export error: "We couldn't export Custom Field Config Scheme"
- JCMA migration error: "CROSS-PROJECT-DATA project-export Plan <id> issue source with type Board has no value"
- JCMA migration error: "project-import We couldn't import Sprint/Board '<sprint/board name>'. Reason: 403 Forbidden"
- JCMA migration failing for application JSU Automation Suite for Jira Workflows
- JCMA Project Migration: Handling NullPointerException
- Migrate filters of Particular Users from Server to Cloud
- Migration of Jira's historical keys for issues and projects
- Migration of service projects fails with database collation errors.
- Migration plan disappeared from the JCMA Migration Dashboard
- Notification based on the event type "18" and "19" is not supported via JCMA migration
- NumberFormatException due to "null" value for the custom field
- project-export error "All project roles are empty"
- Project-import error "We couldn't import Time Metric" due to Bad Request
- Project migration fails while inserting into AO_6FF49D_MIGRATED_FILE table
- Relation "PROJECT" does not exist error : Server to cloud migration
- The migration raises the "missing reference to group - [group_name]" error
- We couldn't export Issue Security Level Permission: Server to Cloud Migration
- We couldn't export Workflow java.lang.NullPointerException: it must not be null
- We couldn't import Portlet Configuration error in project migration
- We couldn't import Project Version because of <Number_of_Occurrences> missing dependencies
- Workflow rules migrated via Jira Cloud Migration Assistant
Related content
- No related content found
Powered by Confluence and Scroll Viewport.