Skip to main content
Skip table of contents

How to migrate WBS Gantt-Chart from Server / Data Center to Cloud

Summary

This is manual how to migrate WBS Gantt-Chart for Jira Server/Data Center to WBS Gantt-Chart for Jira Cloud using Jira Cloud Migration Assistant (JCMA).

Prerequisites for Migration

To perform the migration, WBS Gantt-Chart for Jira Server/Data Center version must be 9.14.0 or higher.
If you are using 9.13.x or lower, please update the app first.

Manual

1. Enable Dark Feature

Currently JCMA’s App data migration feature is not public.
So, until the feature is released as GA, WBS Gantt-Chart for Jira data migration feature is under dark feature which needs user to do enable the feature with special operation.

Atlassian has launched the Early Access Program (EAP) for JCMA.
You can sign up for the EAP at the link below.
http://go.atlassian.com/appmigrationseap

Server / Data Center Side

Please sign up for the EAP and get the procedure manual.

Cloud Side

No special operation is required.

2. Check and Normalize

Server / Data Center Side
  1. Go to Add-ons admin page and go to Cloud Migration page under “WBS GANTT-CHART” section.

  2. Add issue template issue type to every issue type scheme.

  3. If there are template issues which has issue security level, Please clear issue security level from the issue.

Cloud Side
  1. Go to App admin page and go to Migration Information page.

  2. Confirm to be shown “READY” status.

3. Do migration with JCMA

Please follow the Atlassian documentation.

https://confluence.atlassian.com/cloud/use-the-jira-cloud-migration-assistant-to-migrate-from-server-to-cloud-993925215.html

4. Configure WBS Gantt-Chart for Jira Cloud

  1. Go to App admin page and go to Issue setting page.

  2. Configure link setting to migrated ones.

  3. Configure field setting.

Specification

What data is migrated

Data

Note

WBS Code

Limitation

On WBS Gantt-Chart for Jira server version WBS code of a issue can be set each WBS (Gantt WBS, Project WBS, Filter WBS). On the other hand, WBS code of a issue have to be unique on WBS Gantt-Chart for Jira cloud version.

Therefore, If the same issue has WBS code on several WBS (e.g. Issue X’s WBS codes on Gantt A , on Gantt B and on Project C are different), used WBS Code is following priority.

Newer Gantt > Older Gantt > Project > Newer Filter > Older Fileter

Template

Limitation

Only fields of editable standard columns, successors and predecessors are migrated.

Editable Standard Columns

  • WBS code

  • Name

  • Assignee

  • Units

  • Priority

  • Start Date

  • Finish Date

  • Manual Mode

  • Due date

Differences in specifications

On WBS Gantt-Chart for Jira server version, templates are issues.
On the other hand, on WBS Gantt-Chart for Jira cloud version, templates are app own data.
Thus migrated issues for template are meaningless. So they are deleted automatically in migration process. And template issue type also.

Gantt-Chart data such as start date

Migrate data as a Jira field.

Hierarchy and Dependency

Migrate data as a Jira issue link.

Gantt

Migration of gantt data to the cloud is only possible with WBS Gantt-Chart for jira Data Center 9.16.0 or later.
Due to differences in functionality between the Data Center/Server and Cloud versions, some data will not be migrated.
For details, please check "Gantt Data Migration" below.

Jira Cloud Migration Assistant(JCMA) executes the migration to the Cloud without updating the project ID included in the filter's JQL.
As a result, the migrated Gantt chart may not display issues correctly.

Therefore, you need to change the project ID included in the JQL to the project key before migrating to the Cloud, or update the JQL after migrating to the Cloud.

Since this is an issue with JCMA, you will need to watch and vote for the following Atlassian issue and wait for an improvement:
https://jira.atlassian.com/browse/MIG-907

Gantt Data Migration

Data Center / Server item name

Migratable

Note

General

 

  • Gantt name

(tick)

 

  • Administrative users

(tick)

  • Administrative groups

(tick)

  • Operation by non-administrators

(tick)

 

Issue view

 

  • Issue display mode

(error)

The Cloud version does not have this feature.

  • Issue view configuration

(error)

In the Cloud version this exists only in the global settings.
And it is not possible to change the setting for each issue type.

  • Initial planned date

(tick)

 

  • Issue template share project

(tick)

  • Restrictions on using drag-and-drop

(error)

The Cloud version does not have this feature.

Version

 

  • Version management on WBS

(tick)

 

  • Version to display

(tick)

 

  • Option

(tick)

  • Relationship between versions and issues

(error)

The Cloud version does not have this feature.

  • Version manual mode

(tick)

 

Columns

 

  • Standard Columns

(error)

The Cloud version does not have this feature.

  • Extra Columns

(tick)

View

  • Hierarchy link

(error)

In the Cloud version this exists only in the global settings.

  • Dependency link

(error)

In the Cloud version this exists only in the global settings.

  • Warning alert criteria

(error)

The Cloud version does not have this feature.

  • Progress of status

(error)

The Cloud version does not have this feature.

  • Epic

(error)

The Cloud version does not have this feature.

  • Fiscal year start month

(tick)

Color

 

  • Children Bar

(tick)

  • Parents Bar

(tick)

  • Baseline Bar

(tick)

  • Version Bar

(error)

The Cloud version does not have this feature.

Calendar

 

  • Regular Holiday

(tick)

 

  • General holidays

(tick)

 

What data is not migrated

Data

Note

Lag/Lead

Lag/Lead data migration is not supported due to a bug in JCMA that does not correctly convert the issue link IDs.
We are planning to support migration as soon as that bug is resolved.

System Setting

WBS Gantt-Chart for Jira system settings is not migrated. Thus please configure it manually.
They are under “WBS GANTT-CHART” section in Apps admin setting page.

User preference

Notes

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.