To ensure a smooth transfer, please note:
- The Destination Account Should Be Mostly Empty: The account you're copying to should be as empty as possible, with no existing projects.
- Avoid Project Name Conflicts: If a project with the same name already exists in the destination account, it will be skipped during the copy process. No changes or corrections will be made for such overlaps.
- Existing Elements Won’t Be Overwritten: If your destination account already has Workflow statuses, Issue link types, Issue types, Project Roles, or Workflows with the same names as those in the source account, these items will be skipped during the restore process. We won’t delete or update any existing items in your destination account.
- Complete Account Transfer Only: Our service supports copying an entire account at once. We cannot transfer individual items separately.
- User Access: Please ensure all necessary users have been added to your destination account before starting the process. This is important because elements like issues and components reference user data.
Item Type Limitations
To help you understand the copying process, here’s what to expect:
Issue Fields:
- If issue fields already exist in the destination account, they will be duplicated during the copy process. When a new instance is created, a default project and some custom fields are added automatically, resulting in these fields being duplicated.
- We do not copy issue types that have options like multi-select lists.
Issues:
- Fields like "Team" or "fixVersions" cannot be set during the copy.
- If an issue has a reporter or assignee that doesn’t exist in the destination, the issue will be recreated without that user.
- Issues in team-managed projects using custom issue types won’t copy, as there’s no way to create these issue types programmatically.
- Similar to our restore process, issue transitions are limited to one step. For example, transitioning from "To Do → In Progress → Done" is not supported.
Issue Types:
- We can only create issue types of certain hierarchy levels (0, -1). If you have custom hierarchies or have deleted your epic type, these cannot be replicated.
- Custom avatars for issue types are not copied since we currently don’t back them up. However, default avatars (e.g., blue task, red bug) will be applied.
- If the Sub-Task issue type is disabled, we won’t be able to create it as we can't re-enable it through the API.
Projects:
- Project names and keys must be unique. If there's a conflict, the project copy will fail, and issues won’t be created properly.
- Certain team-managed and JPD projects won’t be copied due to a lack of API support.
- JSM projects are not included in the copy process.
Filters:
- Filters can have various permissions (project, organization, user, or group). Since users and groups aren't copied, any filters using these permissions will fail to copy.
- All user and group permissions will be removed from filters during the process.
Screens:
- If a screen assigned to your issues doesn’t use the "General" tab, the layout may appear off in the destination account. This happens because a "General" tab is automatically created, even if your source screen doesn’t use it.
Workflows:
- Workflows with screens that have required fields might encounter issues during transitions, especially if the field complexity is high. If you run into issues with this, please contact our support team at help@rewind.com.