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

Do not base user keys on usernames

XMLWordPrintable

    • 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.

      Current state

      When a new user account is created in Jira, the user key (used as an immutable foreign key in the database) is the same as username, lowercased. For example, user Admin will get a user key admin. If there’s a naming conflict, the user key will be set to a value like ID10100.

      This is problematic, because usernames are often based on full names. As a result, user keys contain personal information that is later scattered throughout the entire database, making GDPR compliance harder.

      Expected state

      User keys in Jira do not contain any personal information, but are somewhat random.

            [JRASERVER-69842] Do not base user keys on usernames

            Daniel Rauf added a comment -

            Starting from Jira 8.4.0, user keys are generated using a new strategy.

            Please refer to https://confluence.atlassian.com/jiracore/gdpr-changes-in-jira-975041009.html#GDPRchangesinJira-userkeys for more details.

            Daniel Rauf added a comment - Starting from Jira 8.4.0, user keys are generated using a new strategy. Please refer to https://confluence.atlassian.com/jiracore/gdpr-changes-in-jira-975041009.html#GDPRchangesinJira-userkeys for more details.

              drauf Daniel Rauf
              drauf Daniel Rauf
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: