...
Whilst JEMHC only retains the most recent 100 webhooks and inbound/outbound mails, we retain the last months worth of ‘audit’ records that something happened, meaning, webhooks, inbound mail and outbound mail. If a user choose to ‘be forgotten’ Atlassian will notify JEMHC and removals of related records will occur.
Common Data Questions
What data is extracted from the Atlassian Cloud?
For inbound, Jira project metadata defining fields that we need to populate. For outbound, we retrieve any data within the typical REST response for the issue, eg /rest/api/latest/issue/ABC-123. In addition, attachment data referred (eg inlined screenshots, but could also be any attached file, if you configure JEMHC to do so!), icons for projects, issue types, priorities, all the things you’d expect in a Jira email.
Is it data in transit or data at rest?
Webhooks are in transit until stored in the JEMHC DB, the time webhooks are ‘in transit’ in the FIFO queue depends on the backlog in the queue. Typically, the queue is empty, and messages are retrieved in a matter of seconds. Once data is retrieved from the queue it is encrypted and stored in the JEMHC DB, considered at rest.
If data at rest, where is it stored.
JEMHC data is currently stored in a highly available dedicated JEMHC database, which is not publicly accessible.
Data Residency
background: https://www.atlassian.com/software/data-residency , non US realms: https://www.atlassian.com/roadmap/cloud?category=dataManagement&
JEMHC currently only has one ‘Realm’, located in the USA, we expect to look into JEMHC data residency later in the year..
Profiles
JEMH Server/DC Profile exports are not currently compatible with JEMH Cloud.
...