Pivot Introduction
Pivot Basics
Tabs
Advanced
3rd Party Support
Tech Stuff
- Connection Troubleshooting
- Debug with HAR files
- Migration to Cloud
- Jira Server POST Size
- Reset Apps Cache on Server/DC
- Security and Privacy Policy
Licensing and Purchasing
Server to Cloud Migration
Server to Cloud Migration Overview
Pivot Report Server to Cloud Migration is done with Atlassian Jira Cloud Migration Assistant. The migration works in a fully automated mode. Please note that Jira Cloud Migration Assistant has certain limitations, and not all types of data are migrated. You can read more about it in this article by Atlassian. That means that all data, required for Pivot Report, will be avaiable in Cloud after migration is complete, and you will need to perform some manual tweaks.
Full guide about Jira Cloud to Server migration with Atlassian Jira Cloud Migration Assistant can be found here.
Pivot Report: Server and Cloud features
Pivot Report is Cloud First app. It means that new features arrive to Cloud first, and then they are added to Server. In terms of features, Cloud version has Issue View integration, which is not presented in Server version. Other than that, Cloud and Server version are identical from the functional standpoint.
What Pivot Report data gets migrated
App settings and all saved reports are migrated. Please check tables below for addional information.
Application Settings
| What is migrated | Notes |
|---|---|
| Projects | Migrated by short name/keys, e.g. PR, WL, TT, etc. Jira Cloud Migration Assistant migrates project keys, but project migration could be partial (not all projects), so you may need to remove app settings projects that are exported to the Cloud |
| Issue Types | Migrated with Jira Cloud Migration Assistant Mapping API. Should work with no extra tweaks |
| Users | Migrated with Jira Cloud Migration Assistant Mapping API. Should work with no extra tweaks |
| Groups | Migrated by the names. Since it’s possible that not all users groups are migrated, you need to remove unused groups after the migration is complete |
| Issue Links | Migrated with Jira Cloud Migration Assistant Mapping API. Should work with no extra tweaks |
Saved reports
Migrated reports will have M label next to the name on the Manage Reports page. This label is removed after you save the report in Cloud.
Source Settings
| What is migrated | Notes |
|---|---|
| Issue | Issues are migrated via keys (e.g. PR-123, WL-456, TT-789, etc.). It’s possible you’ll have to delete some of saved reports, if source projects aren’t migrated |
| Saved Filter | Jira Cloud Migration Assistant support only default filters (e.g. Created Recently) and filters that are used in boards. Other filters are ignored. |
| JQL | Jira Cloud Migration Assistant migrats JQL as a text string. That means all JQLs you use for sources and slices require a manual check after migration is complete. |
| Board | Migrated with Jira Cloud Migration Assistant Mapping API. Should work with no extra tweaks |
| Structure | Not suppoted in Cloud |
Sharing Settings
| What is migrated | Notes |
|---|---|
| Users | Migrated with Jira Cloud Migration Assistant Mapping API. Should work with no extra tweaks |
| Groups | Migrated by the names. Since it’s possible that not all users groups are migrated, you need to remove unused groups after the migration is complete |
Tabs Settings
Tabs configuration is fully migrated: number of tabs, names, order and types. Options of each specific tab though depends on the fields in the target instance, so it’s recommended to check the report after the migration is complete.
Slices Settings
| What is migrated | Notes |
|---|---|
| Custom Fields | Migrated with Jira Cloud Migration Assistant Mapping API. Should work with no extra tweaks |
Hierarchy Settings
| What is migrated | Notes |
|---|---|
| Issue Types | Migrated with Jira Cloud Migration Assistant Mapping API. Should work with no extra tweaks |
| Issue Links | Migrated with Jira Cloud Migration Assistant Mapping API. Should work with no extra tweaks |