Automated Log Work Cloud is an app with more extended capabilities than Server version. The extended capabilities include

Why Migrate to Cloud

extended reports and work log data export
group based access to report data
general and per project configuration
min/max time spent limits reporting limits per day
work logs tags
different automatic timer strategies
extended work log editor
…..

Purpose

This document will give you a guide and information how to migrate Automated Work Log Server to Automated Log Work Cloud JIRA instance.

The Automated Log Work Cloud has many more features than server version. We hope you will enjoy it.

Data automatically migrated

All data related to work logs will be automatically migrated to new Jira instance no further actions are necessary. All work logs and work logs comments will be automatically migrated.

Manual migration of settings

Due to changes in ids of projects and issue types Automated Log Work general settings will not be migrated. The general settings have to be restored on new Jira instance manually.

How to migrate

Before migration on source server JIRA instance

Just before migration on your JIRA instance there might be a few started timers. If timer is started then work time is not yet logged. In such case you have to ask all users to stop timers.

If you do not stop timers values in started/active timers will not be logged and will not be migrated to Cloud. Already logged time will be migrated anyway.

After migration on destination cloud JIRA instance

Restore manually general Automated Log Work settings. In Cloud version you can also configure Automated Log Work for individual projects.

Notes

If you have further questions do not hesitate to contact us at support@gebsun.com or at Gebsun Customer Portal.