Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-66978

GDPR Compliance - Right to be forgotten

    XMLWordPrintable

Details

    • 1
    • 1
    • Hide
      Atlassian Update – 10 January 2020

      Hi everyone,

      In Jira 8.7 we will ship the ability to permanently anonymize a user account and the personally identifiable information associated with it. 

      This will help organizations stay compliant with GDPR and the 'Right to be forgotten'. We’ve already announced some changes in previous Jira versions, now we’re making them happen. You can read more about user anonymization in Jira in the documentation.

      Starting from Jira 8.7.0 you can anonymize users in two ways — the choice here depends on whether the user still exists, or has been deleted.

      Active users:

      • Go to Administration > User management > Users.
      • Find the user you want to anonymize, and select … > Anonymize user.

      Deleted users:

      • Go to Administration > User management > Anonymization.
      • Enter the username, and select Anonymize.

      To learn more about what’s coming in Jira 8.7, read Preparing for Jira 8.7.

      We will change the status of this suggestion when Jira 8.7 is available. At the moment, you can download our latest EAP version for Jira Software and Jira Service Desk. Portfolio for Jira will also support user anonymization.

      For customers on earlier Jira versions, please check out our GDPR support guides and for anonymizing user activity JIRA: Right to erasure. For versions 8.7.0 and the upcoming ones, we recommend the in-product user anonymization.

      Katarzyna Derenda
      Product manager, Jira Server and Data Center

      Show
      Atlassian Update – 10 January 2020 Hi everyone, In Jira 8.7 we will ship the ability to permanently anonymize a user account and the personally identifiable information associated with it.  This will help organizations stay compliant with GDPR and the 'Right to be forgotten'. We’ve already announced some changes in previous Jira versions, now we’re making them happen. You can read more about user anonymization in Jira in the documentation . Starting from Jira 8.7.0 you can anonymize users in two ways — the choice here depends on whether the user still exists, or has been deleted. Active users: Go to Administration > User management > Users. Find the user you want to anonymize, and select … > Anonymize user. Deleted users: Go to Administration > User management > Anonymization. Enter the username, and select Anonymize. To learn more about what’s coming in Jira 8.7, read Preparing for Jira 8.7 . We will change the status of this suggestion when Jira 8.7 is available. At the moment, you can download our latest EAP version for Jira Software and Jira Service Desk. Portfolio for Jira will also support user anonymization. For customers on earlier Jira versions, please check out our  GDPR support guides and for anonymizing user activity  JIRA: Right to erasure . For versions 8.7.0 and the upcoming ones, we recommend the in-product user anonymization. Katarzyna Derenda Product manager, Jira Server and Data Center
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      With some of the access controls we already have, is there any planning from Atlassian on adding deletion features to Jira tickets? As of now we have bug tickets that do contain bits of member PII.

      If that member files a rights to be forgotten, there is no current solution we have found to honor that request if their information was ever filed in Jira ticket. 

      Attachments

        Issue Links

          Activity

            People

              tkanafa Tomasz Kanafa
              e73e2a94444b Sean Patrick
              Votes:
              12 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: