Book
Books Back to Homepage
ZenTao Open-Source 15.0
More
1 Download and Upgrade to 15.0+ Series
2 New Features of ZenTao 15 Series
3 Interface Changes of 15 Series
4 Update to the Latest Version
5 Quick Start of 15 Series
6. Basic Application of Version 15
6.1 Beginner
6.2 Add Integrally
6.3 API Library
7. Base On The Roles
7.1. Admin
7.1.1 Edit Departments and Team Members
7.1.2 Edit Users
7.1.3 Edit Privilege
7.2. Program Leader
7.2.1 Create a Program
7.2.2 Link to Products
7.2.3 Create a Project
7.2.4 Manage Staffs
7.2.5 Add a Program Stakeholder
7.3. Product Owner
7.3.1 Create a Product
7.3.2 Edit Modules
7.3.3 Product Multi-branch/Platform Management
7.3.4 Edit Plans
7.3.5 Edit Stories
7.3.6 Review a Story
7.3.7 Create a Release
7.3.8 Tracking Progress
7.4. Project Manager
7.4.1 Edit Projects and Execution
7.4.2 Edit Teams
7.4.3 Link to Stories
7.4.4 Split Tasks
7.4.5 Tracking Progress
7.4.6 Waterfall Project
7.4.7 Kanban Project
7.5. Development Team
7.5.1 Apply for Tasks and Bugs
7.5.2 Update Status
7.5.3 Complete Tasks and Bugs
7.5.4 Submit Codes
7.5.5 The General Kanban, Story Kanban, Bug Kanban, and Task Kanban
7.6. Test Team
7.6.1 Edit Users' Case
7.6.2 Execute Users' Case
7.6.3 Submit a Bug
7.6.4 Test and Close a Bug
8. DevOps Features
8.1 Git/SVN Repository Management and Viewing Code
8.2. Integrate GitLab
8.2.1 Integrate GitLab, Bind Users, Link to Issues and Create a Build
8.2.2 Integrate GitLab and Submit the Merge Requests
8.2.3 GitLab Privilege in ZenTao
8.3 Integrate Jenkins and Create a Build
8.4 Integrate SonarQube
9 General Kanban
10. Backstage Settings of Version 15
10.1 Desktop
10.2 Model
10.3 Custom
10.4. Message
10.4.1 Mail
10.4.2 Webhook
10.4.3 Browser
10.4.4 Settings
10.5 Extension
10.6 Secondary Development
10.7 System
10.8 Jira Data Migration Checklist and FAQ
10.9 Data Migration from Jira
10.10 Data Migration from Confluence
10.11 Registration Menu and Privilege
11. Privileges Management and Access Control of Version 15
11.1 Privileges Management and Access Control for Programs
11.2 Privileges Management and Access Control for Products
11.3 Privileges Management and Access Control for Projects
11.4 Privileges Management and Access Control for Executions
11.5 Access Control and Data Relationships for Projects and Executions

Jira Data Migration Checklist and FAQ

23
Kelsea
2025-07-23 09:46:36
Share links

Jira Data Migration Checklist

Type Features and Data of Jira Features and Data of ZenTao Migration Overview Notes
User Management Users Admin - User Support Supports Migration of Usernames and Emails
User Management Groups Admin - User Requires Reconfiguration There are significant differences in permissions between Jira and ZenTao, requiring reconfiguration of permissions and groups.
Notification Notification Admin - NotificationRequires Reconfiguration Requires Reconfiguration The notification systems of Jira and ZenTao differ greatly, necessitating a reconfiguration of notification settings.
Automation Automation Rules Engine Requires Reconfiguration There is a notable disparity in functionality between Jira and ZenTao, requiring a reconfiguration of rules.
Jira Project Data Project Name Project Name Support  
Jira Project Data Project Lead Project Manager Support  
Jira Project Data Project Type Project Type Support After importing Jira projects, all projects will be categorized as product-based Agile projects.
Jira Project Data Project Roles Project - Settings - Team Requires Reconfiguration Reconfiguration required post-import.
Jira Project Data Project Users Project - Settings - Team Support Team members
Jira Project Data Sprint Sprint Support If there are requirements and tasks within the project that are not linked to an Sprint, they will automatically be assigned to the Sprint that shares the project's name.
Jira Project Data Release Release Support After migration, these will be converted into releases, and a build with the same name will be created.
Jira Project Configuration Issue Type Scheme Workflow - Project Support Unarchived projects will automatically create a project workflow template upon migration, with configuration items being incorporated into this template.
Jira Project Configuration Field Configuration Workflow - Project Limited Support Fields that have been used will synchronize their properties, while unsupported formats will be adjusted for compatibility. Migration of default items and required field settings is currently not supported.
Jira Project Configuration Issue Type Screen Scheme Workflow - Project Requires Reconfiguration Reconfiguration can be performed in ZenTao after migration.
Jira Project Configuration Workflow Cache Workflow - Project Support Migration of workflow statuses and steps is supported, but triggers, condition validations, validators, and subsequent actions cannot currently be migrated.
Jira Project Configuration Permission Schemes Project - Settings - Privilege Requires Reconfiguration There are significant differences in permissions between Jira and ZenTao, requiring reconfiguration of permissions and groups.
Jira Issue Configuration Issue Type Workflow - Object Support Based on the selection made during import, data will be synced to either built-in objects or newly created objects.
Jira Issue Configuration Feild Workflow - Feild Support Built-in fields and custom fields with existing data (according to the import selection) will be synced to built-in fields or new objects.
Jira Issue Configuration Statuses Workflow - Status Support Depending on the import selection, data will sync to built-in statuses or the statuses of newly created objects.
Jira Issue Configuration Priorities Admin - Feature - Priority Support Automatic synchronization enables the setting of different priorities for various objects in ZenTao.
Jira Issue Configuration Issue Linking Admin - Feature - Relation Support Depending on the selection during import, relationships will be synced to either built-in or newly established associations.
Jira Issue Configuration Resolution Admin - Feature Support Closure reasons corresponding to ZenTao Bugs, requirements, tasks, feedback, and tickets will be included.
Jira Issue Data ID ID Support  
Jira Issue Data Project Project Support  
Jira Issue Data Issue Type / Support Different types of issues imported into ZenTao correspond to various objects.
Jira Issue Data Summary Title Support  
Jira Issue Data Status Status Support  
Jira Issue Data Priority Priority Support  
Jira Issue Data Sprint Sprint Limited Support New objects are linked to projects and do not include the associated Sprint field.
Jira Issue Data Description Description Support  
Jira Issue Data Fix Version/s Link to Release Limited Support They will be displayed under the corresponding release, with only sub-requirements and bugs shown; information for other issues will not be imported as closure reasons for ZenTao Bugs, requirements, tasks, feedback, or tickets.
Jira Issue Data Resolution Close Reason / Resolution Support  
Jira Issue Data Creator Create by Support  
Jira Issue Data Assignee Assignee Support  
Jira Issue Data Reporter Reporter Support The system will automatically generate these.
Jira Issue Data Watchers Watchers Support The system will automatically generate these.
Jira Issue Data Date Created Create Time Support  
Jira Issue Data Date Updated Update Time Support The system will automatically generate these.
Jira Issue Data Due Date Deadline Support The system will automatically generate these.
Jira Issue Data Attachments Attachments Support  
Jira Issue Data Issue Links Linked Object Support  
Jira Issue Data Sub-tasks Sub-object Limited Support Requirements and tasks support a parent-child hierarchy, while other objects will record their parent-child relationships, which can be viewed in the relationships section.
Jira Issue Data Comments History - Comment Support  
Jira Issue Data Esitmated, Logged Estimation, Cost Limited Support Built-in objects support both work hour values and records, whereas new objects only support work hour values.
Jira Issue Data Customized Feild Customized Feild Support  

FAQ

  1. Data Import Timeout

    Please check the server's Apache or Nginx for any resource shortages and adjust the configuration as needed.

  2. Description Format After Import Differs from Before

    The ZenTao editor supports only text, images, and links; other formats will be rendered as HTML styles.

  3. Fewer Fields After Import Compared to Jira System

    The system only imports fields that have been used; unused fields will not be included. Users can add these fields in the workflow.

    Additionally, version-related issues may arise; if using the open-source version, only built-in fields are supported, and new fields cannot be added.

  4. An Additional Sprint with the Same Name Appears Under the Project After Import

    If there are issues within the project that lack an assigned Sprint, the system will automatically create a Sprint with the same name as the project to accommodate these issues.

  5. Error Message During File Import Indicates Inability to Connect to API

    This could be due to an incorrect domain name being entered, potentially using an IP address; it may also indicate that API call authentication has not been enabled.

  6. User Permissions Did Not Transfer Successfully

    There is a significant difference in permissions between Jira and ZenTao, necessitating that users reconfigure their permission groups.

  7. Unable to Log into Account

    ZenTao accounts do not support special characters other than underscores. For users migrating from the cloud version, if the account name is particularly unique, you may opt to use the email address as the username.

  8. Field Format After Import Differs from Previous Format

    If existing fields are selected for import, only the data will be imported without changes to the format. If new fields are created, the format will adapt to either single-line text or single-choice dropdown, depending on the availability of options, in addition to what the workflow supports.

  9. Historical Records Not Displayed

    Historical records are currently not supported for migration.

  10. Story Points Not Displayed

    The story points field must be manually mapped.

  11. Actions Not Displayed After Import

    Imported actions are disabled by default. If you wish to use them, please enable them in the workflow.

  12. User Seats Exceed Authorization Limit

    If user seats exceed license authorization, the import will be terminated, and they will be unable to log in. Please contact us at [email protected] to get more user seats.

  13. Multiple Requirements/Tasks/Bugs Appear When Matching Objects

    The IDs of requirements/tasks/bugs in Jira cloud version team-level projects differ from the system's default IDs and will all be recognized.

  14. Import Error: SQLSTATE[42000]: Syntax Error or Access Violation: 1118 Row Size Too Large

    Before importing, run the following command in the database: SET GLOBAL innodb_strict_mode = OFF, and then proceed with the import.

  15. For Additional Issues, Please Contact Us.

Write a Comment
Comment will be posted after it is reviewed.