Sanplex supports importing data from Jira. Sanplex also supports migrating Jira new Issue types, custom fields, and workflows. For security reasons, this feature is available to Super Admins only.

【Jira数据迁移到禅道的视频介绍】

I. Prepare Jira Data

Supported Jira Deployments

• Jira Software Server / Data Center
• Jira Software Cloud

Supported Jira Versions

• Jira Server: 7.x, 8.x, 9.x, 10.x

1. Clean Up Jira Data (Recommended)

• Before migration, delete Jira accounts that are no longer used. If the same user already exists in Sanplex, ensure the Jira account, Sanplex account, and email address are consistent.

• Remove unused Issue types and unused attributes/fields in Jira to speed up mapping and reduce migration time.

• Review project statuses:

  • Archive completed projects.

  • Move projects you do not plan to import to the Recycle Bin.

  • After import:

    • Archived Jira projects are imported as Closed in Sanplex.
    • Projects in Jira’s Recycle Bin are not imported.
    • Other projects are imported as In Progress.

2. Export Jira Data

Sanplex supports migrating Jira data via database import or file import.

2.1 Jira Database Backup

Ask the Jira database administrator to back up/export the Jira database and attachments.

Note: Due to Jira database schema changes introduced in Jira 8.8, database import supports Jira 8.8 and later. For earlier versions, upgrade Jira first or use file export/import.

2.2 Export Jira Cloud Backup File

Export path: Jira Settings > System > Backup manager > Create backup for cloud > Download cloud backup

图1

II. Prepare Sanplex

1. Prepare the Sanplex Environment

Ensure your Sanplex deployment is installed and updated to a build that includes Jira data import.

If you need to migrate new Jira Issue types, custom fields, and workflows, ensure the corresponding migration capabilities are enabled in your Sanplex deployment.

2. Back Up Sanplex Data

If Sanplex is already in use, back up the Sanplex database before importing.

During backup and the Jira import process, it is recommended to stop using Sanplex temporarily to prevent conflicts or data loss.

III. Import Jira Data

1. Entry Point

Go to Admin > Data Import > Import from Database.

图2

2. Choose an Import Method

Jira import supports two modes:

• Import from Database (recommended for self-hosted Jira deployments)
• Import from File (recommended for Jira Cloud or when database access is unavailable)

2.1 Import from Database

Go to Admin > Data Import > Import from Database to enter the pre-import page.

Follow the on-screen instructions to place the required files and attachments into the specified directories.

After entering Jira database connection details, click Next to start data matching.

图3

2.2 Import from File

Go to Admin > Data Import > Import from File.

Create a folder named jirafile under the Sanplex tmp directory, and ensure the jirafile folder has read/write permissions.

After completing the above steps, click Next to proceed with data matching.

图4

Note: If you want to import iteration/sprint data, you must provide the Jira environment domain, admin account, and password / token.

• Domain: enter only the base domain/host, for example:

  • Correct: https://ABC.atlassian.net/ or http://11.1.1.118:8/
  • Incorrect: https://ABC.atlassian.net/jira/settings/issues/issue-types

• Jira Cloud uses an API token (create it in the Atlassian account security settings). Other deployments typically use a password.

图5

图6

3. Map Jira Objects to Sanplex Objects

Because Jira Issue types, fields, statuses, resolutions, and link types can be customized, you must configure mapping before import.

• Step 1: map Jira Issue types to Sanplex objects. Common target objects include User Requirements, Software Requirements, Tasks, and Bugs. Sanplex also supports mapping to Feedback, Tickets, and Workflow objects where applicable.

• When selecting a mapping, you can choose Create as Workflow Object. If selected:

  • Sanplex automatically creates a new workflow object during import.
  • Field/status/resolution mapping is handled automatically and does not require manual configuration.

• Sanplex provides default mappings to help you import quickly. You can adjust the defaults as needed.

• Unused Issue types (never used in Jira) are filtered out and will not be displayed for mapping.

图7

4. Map Issue Fields to Sanplex Fields

Configure field mappings per Issue type.

• If you choose Create New, Sanplex creates a new field during import.
• Unselected fields are not imported.
• Built-in Jira fields are handled by default and may not appear on the mapping page; the page lists only custom fields that actually contain data.

图8

5. Map Issue Statuses to Sanplex Statuses

Map Jira Issue statuses to Sanplex statuses, such as:

• Requirement status/stage
• Task status
• Bug status
• Feedback status
• Ticket status

Defaults are provided. You can modify them.

If no mapping is selected, Sanplex applies default statuses after import (for example: Requirement = Active, Stage = Not Started; Task = Not Started).

图9

6. Map Issue Resolutions to Sanplex Values

Map Jira Resolution values to:

• Bug resolution
• Closure reasons for requirements/tasks/feedback/tickets

Defaults are provided. You can modify them.

• If you choose Create New, Sanplex creates the resolution value during import.
• If no mapping is selected, imported items default to Done/Completed (as applicable).

图10

7. Configure Global Link-Type Mapping

Map Jira Issue link types to Sanplex relationship types.

• You can map to an existing relationship type or choose Create New.
• Unmapped relationship types are not imported.

图11

Recommended relationship mappings are shown in the figure below. Other relationship types can be mapped or added as needed.

图12

8. Configure Jira Users

Set imported users’ default Sanplex password and permission group.

• Username source can be Jira account name or Jira email; using the Jira account is recommended.
• If an imported username matches an existing Sanplex username, Sanplex merges them into one user. Review usernames beforehand to avoid unintended merges.
• Because encryption algorithms differ, imported Jira users will use the default password defined on this page.

图13

9. Start Import

After setting the default password and permission group, click Next to open the final import page.

图14

Click Start Import. Import may take some time.

图15

When all objects are imported successfully, the system displays Import Successful, and the Jira data import is complete.

IV. Feature Mapping Reference

Below is a reference mapping between Jira and Sanplex features. Use the linked manuals for details.

| Category            | Jira                              | Sanplex                         | Reference Manual |
|--------------------|-----------------------------------|----------------------------------|------------------|
| Project features   | Project                           | Project                          | https://www.zentao.net/book/zentaopms/1597.html |
| Project features   | Sprint                            | Iteration                        | https://www.zentao.net/book/zentaopms/890.html |
| Project features   | Release                           | Release                          | https://www.zentao.net/book/zentaopms/888.html |
| Project features   | Permission Schemes                | Project > Settings > Permissions | https://www.zentao.net/book/zentaopms/482.html |
| Issue types        | Epic                              | User Requirement                 | https://www.zentao.net/book/zentaopms/886.html |
| Issue types        | Story                             | Software Requirement             | https://www.zentao.net/book/zentaopms/886.html |
| Issue types        | Task                              | Task                             | https://www.zentao.net/book/zentaopms/891.html |
| Issue types        | Bug                               | Bug                              | https://www.zentao.net/book/zentaopms/897.html |
| System features    | Users                             | Admin > Personnel Management     | https://www.zentao.net/book/zentaopms/1009.html |
| System features    | Issue Type                        | Workflow > Objects               | https://www.zentao.net/book/zentaopms/workflow-1534.html |
| System features    | Field                             | Workflow > Fields                | https://www.zentao.net/book/zentaopms/workflow-1534.html |
| System features    | Statuses                          | Workflow > Statuses              | https://www.zentao.net/book/zentaopms/workflow-1534.html |
| System features    | Screen Scheme                     | Workflow > Pages                 | https://www.zentao.net/book/zentaopms/workflow-1534.html |
| System features    | Notification                      | Admin > Notification Settings    | https://www.zentao.net/book/zentaopms/999.html |
| System features    | Priorities                        | Admin > Feature Configuration    | https://www.zentao.net/book/zentaopms/1624.html |
| System features    | Issue Linking                     | Admin > Relationship Types       | https://www.zentao.net/book/zentaopms/browseRelation-1576.html |
| System features    | Resolution                        | Close Reason                     | https://www.zentao.net/book/zentaopms/1624.html |
| System features    | Automation                        | Rules Engine                     | Documentation to be released separately |