Versions Compared

Key

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

The Scheduler for Jira Cloud:

...

We are leveraging Amazon Web Services to store our data (particularly we are using relational db deployed on AWS RDS and Kibana for data logs visualizations - also served by AWS side). According to AWS GDPR center - AWS has announced compliance with the CISPE Code of Conduct and demonstrating compliance with rigorous international standards, such as ISO 27017 for cloud security, ISO 27018 for cloud privacy, SOC 1, SOC 2 and SOC 3, PCI DSS Level 1 and others. Your data on AWS used for processing The Scheduler scheduled jobs is secured in highest manner possible. We are not sharing or exposing those data to any 3rd party legal entity or partners.

...

For the self-hosted data, we maintain a daily backup of our relational DB schema, so that in case of a disaster, we could re-create your data. However, in order to provide additional availability and to further minimize any data loss, we keep a standby database replica that stays in sync with our primary database and is fully capable of taking over in case of a primary database failure.

Migration from server to cloud concerns

Due to the fact that we have recently rolled out automatic migrator enabling migrating data from The Scheduler on server/data center instances to its cloud counterpart - brief overview of whole process and data processing activities that we perform can be found below.

  • At the begging of the whole process of migration Issue Templates are being sent to S3 managed by Atlassian
  • During data mapping we are using Issue Templates stored in aforementioned S3 bucket in order to create templates on Jira Cloud (although they are transited through our cloud infrastructure they are not persisted on our side)
  • During and after migration is completed - logs are gathered (accessible for Administrators of respective instances that were subject to a migration activities - in order to enable investigation of potential problems that may occur during data migration) containing data as follows:
    • project id, client key, scheduled issue name, sub-task name, custom fields id


...


The Scheduler for Jira Server and Data Center:

...