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

As an admin, allow me configuring what user's information is shared between users

XMLWordPrintable

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

      There are several scenarios where user's username and email are shown. This can be considered a security risk for some customers.

      Examples:

      • When doing a user search, a suggestion list appears while writing, this list includes the user display name, email and even username.
      • From the issue view, any user can see another user's profile, which shows all the information of the user.

      Similarly suggested for Confluence, the suggestion is allowing a way to control the access to this information (like only showing display names for non-admin users) or using the following as an example:

      1. A user is only allowed to see the name and profile of another user if they are in the same group. (at least one group, not all)

      2. Allow a global administrative option for enabling/disabling user names and profiles.

      3. Allow each user to decide whether their username, email and/or profile should be viewable.

            [JRASERVER-66161] As an admin, allow me configuring what user's information is shared between users

            Gosia Kowalska added a comment -
            Atlassian Update – 01 October 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 01 October 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

              Unassigned Unassigned
              rchiquete Rene C. [Atlassian Support]
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: