Page Comparison

Table of Contents

...

Introduction

We are happy to offer Label Manager for Jira Cloud. Unfortunately due to technical limitations (see below), we currently cannot offer an automated migration path and some manual work is necessary.

To migrate you have to export the field data to .csv, perform some transformations in the .csv field and import the data into Cloud.

Info
Feel free to contact our support desk, if you have further questions or need assistance with your migration.

Migration Steps

1. Add Label Manager Addon in Jira Cloud Instance

We do support migration licenses for our apps. Please reach out to our support if this applies to you.
Note: Our app trial period comes without functional limitations so you can start already.

2. Add the Label Manager Custom Fields

Use the Jira native custom field interface to create the lable label manager custom fields used in onPrem on-premise on the cloud instance. You can add the labels via comma separated list. If you are using project specific configuration, you have to set this up to via the UI.

3

...

Label Manager on Jira Cloud supports bulk adding of label options using comma separated syntax.

Option 1:

Copy paste existing labels from the UI in onPrem into CSV
Migrate the Labels into comma separated list
Add comma separated list in bulk in Jira Cloud to the specific field in Label Manager Global Settings

Option 2:

Get the existing labels form onPrem via API
Migrate the Labels into comma separated list
Add comma separated list in bulk in Jira Cloud to the specific field in Label Manager Global Settings

4. Add Project specific configuration if used

If any project is using specific configuration, go into project settings and update the configuration accordingly.

Just like step 3.

5. Export the Issues from OnPrem in CSV

TODO Alles auf einmal? Projekt spezifisch, Custom field spezifisch?

Export issues in onPrem to CSV.

6. Update the field values in csv using provided excel script

Label Manager fields in OnPrem are using a different field value object structure than in cloud.

Therefore it is necessary to update the field values in the exported csv before importing to cloud.

TODO: Migration script in csv

7. Import the updated csv into Jira Cloud

TODO: normal user csv import ODER admin csv import.

...

. Export Issues

Export Issues via CSV export from on-premise.
Only the fields “Key”, “Label Manager Field” and “Summary” are needed.

4. Convert format in the CSV-file

In the exported CSV you have to convert the data format to the one used in cloud (we weren’t able to use the same format), we can provide you with a formula/infos for Google Sheets/Excel to do this (see below).

Please note that if the issue key changes during your cloud migration, you will have to change this as well in the .csv file.

5. Import Issues to Cloud

Use the CSV import to update/create the new Issues with the converted Label Manager Field data

Data Formats

Anchor

	data-format
	data-format

Server

Label Manager uses a multi-select field type.

For each label selected in the field, a new column is created in the .csv export.

Cloud

Label Manager fields on cloud use an object field type using the following structure.

Cloud Field Value Example:

Code Block

language	json

{"labels":["label-2","label-3",""],"colors":["grey-light","grey-light","grey-light"],"labelSource":"global"}

Note: For project specific label manager configuration, use "labelSource":"project".

Note: "grey-light" is the default color, you have to extend the amount of "grey-light" strings in the array based on the maximum amount of columns the label field uses in the csv.

CSV Value Transformation

...

Using google sheets to work with CSV we came up with the following formula to transform the selected labels into a new column that you can map on the labels field in the Jira cloud instance.