Migration of ActivityTimeline from Jira Server/DC to Jira Cloud

The Jira landscape is evolving, and with Atlassian's announcement to phase out Jira Server in favor of Jira Cloud, users of the add-on ActivityTimeline may be wondering ‘What does this mean for their setup?’

The transition to Jira Cloud will impact not only Jira itself, but also any add-ons, including ActivityTimeline. As a result, users of ActivityTimeline will need to migrate to the cloud-based solution in order to continue using the add-on. This guide is specifically designed to help users of the ActivityTimeline add-on navigate the migration process to Jira Cloud, ensuring a smooth transition and uninterrupted use of the add-on.

Data Migration

When migrating from Jira Server to Jira Cloud with help of Jira Cloud Migration Assistant app, it is important to consider the migration of all data related to your projects and issues. With the ActivityTimeline add-on, all issues and related information such as users and custom fields will be automatically migrated if you transfer all data from Jira Server to Jira Cloud.

Configure ActivityTimeline

Once the migration from Jira Server to Jira Cloud has been completed, the next step for users of the ActivityTimeline add-on is to install and configure the add-on in their new cloud-based Jira instance. This process will require some effort, as all previous configurations, such as user roles, workload schemes, holiday schemes, teams, and skills, will need to be recreated in the new setup. While this may seem like a daunting task, it is a necessary step to ensure the continued use of ActivityTimeline in the Jira Cloud environment.

ActivityTimeline Getting Started Guide may help to remind you how the initial setup needs to be done and what configurations are important to set at the beginning of the way.

It is important to note that while the process of reconfiguring ActivityTimeline may require some time and effort, it also provides an opportunity for users to review their previous configurations and make any necessary updates or improvements.

Scheduled Issues on the Calendar

If you already have issues scheduled on the calendar and would like them to appear automatically, you need to make sure that Start/End date fields from your Jira are mapped to ActivityTimeline:
https://activitytimeline.atlassian.net/l/c/Xab1bmmm

1. Navigate to Configuration → Jira Integration page

2. Make sure fields mapped to ‘Planned Issue Start Date’ and ‘Planned Issue End Date’ are the same:

Open

Custom Events Migration

The migration of the remaining data such as custom events (Ex. Bookings, Placeholders, Days off, etc.) requires manual intervention and will need to be migrated manually by entering the data through the UI. It is a necessary step to ensure that all relevant data is properly transferred to the new Jira Cloud environment.

Feature Comparison

ActivityTimeline Cloud and Server/Data Center provide almost the same feature set (with even a slightly more possibilities in the Cloud version), giving you full access to a comprehensive suite of tools for managing your projects and resources.

In conclusion, the migration of Jira Server to Jira Cloud requires not only the transition of the core Jira platform but also the migration of any installed add-ons, including ActivityTimeline. While the process of reinstalling and re-configuring ActivityTimeline may require some effort, it is a necessary step to ensure the continued use of the add-on in the new cloud-based environment.