Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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:

  • No customer generated data is persistently stored on the external database

    we only persistently store the transaction-

    Persistently stored data on an external database

    • the Atlassian Connect framework automatically tracks the Cloud-ID and instance url. This is not controllable on our side

    • we additionally persist the Cloud-ID and the transaction IDs that Atlassian attaches to migration requests to allow better status tracking for debugging as well as continuous operations for larger instances.

    • this is necessary to handle possible duplicate requests and cancellation requests

    • the transaction - ID for a migration is deleted once the migration has is successfully completed

  • Customer 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 the Forge our Cloud app format and store it in the target Jira Cloud instance

    • this data is only ever accessed when migration requests from the Atlassian 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

...