Service impacting changes: GDPR for Jira Cloud / Legacy Connector EOL Impact

By Jason posted 11 days ago

  

Document Changelog -

01/08/2019 EDIT - Applied new information to Hub versions and availability estimates -JBrown



Jama-Jira-LogoUpcoming Atlassian change


What this means for Admins:

  • All Admins should review their existing Jama to Jira user linking strategy as the risk of impact due to this GDPR change is High.
  • Jira Cloud users – Review the information and begin planning for migration to GDPR supported Opshub and Tasktop versions (when released). Failure to migrate may cause sync downtime if user data is included in a shared data element.
  • Jira Self Hosted – While these changes do not impact Self-hosted (non-cloud) Jira users, this info should be included in review for future local update planning. 
  • Jama's Legacy Jira Connector users Will NOT receive adapter code updates due to previously announced End of Life (EOL)
    See notes below about this change and EOL reminder info!


Details
Earlier in 2018 Atlassian announced modifications to how user data is shared, in effort to follow GDPR. An end date (March 29th, 2019) has been announced, indicating that deprecating user data fields will be completely removed from Jira Cloud API responses. Provided below is a snippet of the official announcement from Atlassian followed by an external link to the complete announcement:

  • By 29 March 2019, we will remove personal data from the API that is used to identify users, such as username and userKey, and instead use the Atlassian account ID (accountId). Additionally, will be restricting the visibility of other personal data, such as email, in conjunction with a user’s profile privacy settings, or in the case of managed account, the visibility settings decided by the site administrator.
As a result of this news - provided below are additional details.

                                                                   

Technical Actions

_________________________

Jama Jira Connector orgs (Legacy JLC) - 
Early in 2018 Jama announced that end of support for the Legacy Jira Connector (04/30/2019). 
Due to the Atlassian change, Jama Legacy EOL support for onPrem (self-hosted) users of the connector will still be the last day of April, but Jama will NOT be making changes to the retiring code. As such, April 2019 will be out of support for all Legacy users, but March will cause strong immediate impact to Jira Cloud users who sync users.
  • Jama STRONGLY RECOMMENDS that customers actively using the Legacy Jira Connector select an alternative connector (such as Opshub or Tasktop).
    • Please reach out to your Account Manager and immediately begin redeployment efforts. In the planning phases, make sure to account for an additional redeployment when the Atlassian changes are available for the hub provider of your choice. 
    • Orgs who have access to the Legacy Connector but DO NOT use it should reach out to your Account Manager and let us know.
    • Waiting until the Hub services release the GDPR versions to begin conversations is not recommended as this will put strain on your timeline.
  • On-Premises (self-hosted) Jira users should not ignore this messaging as future Jira updates locally will be impacted and the Legacy connector will be out of support.


Opshub orgs - 

The Opshub team advises the service version supporting the Atlassian AccountID will be completed in Late January. 
  • OnPrem redeployment to this version will be required in order to get the new code updates.
  • Once the onPrem version is released, Opshub will announce the timing for Cloud instance redeployment.
  • Redeploy is expected to be Mainly Automated with minimal to Zero manual effort to accommodate the change.
  • OIM Version number V7.11 and availability late January (confirmation TBD).
  • Watch this space for information about version availability and needed changes at the time of version redeployment.


Tasktop TIH/JIH/Sync orgs - 
The Tasktop team advises the service version supporting the Atlassian AccountID will be completed in January. 
  • OnPrem redeployment to this version will be required in order to get the new code updates. Due to the sheer number of Tasktop revisions available, only the LATEST revisions of Tasktop will include the GDPR updates. 
  • Watch this space for information about version availability and needed changes at the time of version redeployment.
    • All users of the Tasktop Integration Hub (TIH) will need to migrate to TIH version 19.1 or the latest revision of current versions. Full range of support Versions TBD.
    • All users of the Jama Integration Hub/Tasktop Sync (JIH) will need to migrate to JIH Current versions (full range of support versions TBD) to carry GDPR AccountID support.

_____________________

Other Suggested Actions

Scenario: Active user removal
Synchronizing data between services with “created by” and “modified by” comes with some difficulties where a user removed from only one system can leave conflict actions or errors. This scenario will be worsened with the new changes as GDPR allows a user to hide their “Display name” and email address. This could leave some tickets with only an AccountID for display.


Instead, Jama suggests using an admin account as the default for all Sync functions and rely on the object trace and History to see who and what changes were made. (eg: changed by “Opshub sync” or “Tasktop sync”)
0 comments
38 views