/
Information on processing of data

Information on processing of data

Here are the most important points in regards to what data is used in what way and which data is stored persistently on an external database:

  • Persistently stored data on an external database

    • information about the target cloud instance (e.g. url, clientKey, and a shared secret to request Jira REST APIs for the cloud instance) – gets deleted after uninstalling the migration helper app again

    • we additionally persist information about the migration (name, transfer id, amount of migrated/maximum data to migrate) to allow better status tracking, troubleshooting, possible duplicate requests and cancellation requests

  • Other customer generated data is non-persistently stored on external services only for the duration of the migration

    • issue data is loaded via a JQL query to specifically identify issues which have a Agile Hive hierarchy issue-link

    • this data is only non-persistently stored in RAM

    • this is necessary for the AHCMH app to transform the data from the on premise format to our Cloud app format and store it in the target Jira Cloud instance

    • this data is only ever accessed when migration requests from the Jira Cloud Migration Platform are sent to the ACHMH App

  • Some meta data is persistently logged for troubleshooting

    • total number of issues to migrate

    • number of issues migrated

    • IDs of migrated issues

    • error information from requests to the Jira Cloud instance

    • this data allows us to identify the scope and possible cause of issues that occurred during migration

    • this data is only accessed for error analysis and performance analysis