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

Ability to restrict what users or groups appear in @-mention results

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

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Using an @-mention will list all users, but it would be convenient to be able to restrict that to certain groups, or toggle certain users so that they do not appear in this list.

            [JRASERVER-37386] Ability to restrict what users or groups appear in @-mention results

            8075761753c3 - as the issue is defined here it is clearly about @mention feature which can be configured via permission schemes. Also note that this issue is defined for Jira Server and Data Center and in your comment you are referring to Jira Cloud. I think this would be the issue for Jira Cloud: https://jira.atlassian.com/browse/JRACLOUD-37386

            Maciej Swinarski (Inactive) added a comment - 8075761753c3 - as the issue is defined here it is clearly about @mention feature which can be configured via permission schemes. Also note that this issue is defined for Jira Server and Data Center and in your comment you are referring to Jira Cloud. I think this would be the issue for Jira Cloud: https://jira.atlassian.com/browse/JRACLOUD-37386

            This issue is closed and even though the mentions are limited - clients can still access full user list through:
            https://ACCOUNTNAME.atlassian.net/secure/popups/UserPickerBrowser.jspa

            The current situation provides false sense of a fixed security issue (which is still there).

            Marcin Wasłowicz added a comment - This issue is closed and even though the mentions are limited - clients can still access full user list through: https://ACCOUNTNAME.atlassian.net/secure/popups/UserPickerBrowser.jspa The current situation provides false sense of a fixed security issue (which is still there).
            Maciej Swinarski (Inactive) made changes -
            Component/s New: Administration - Permission Helper [ 43321 ]
            Labels Original: affects-cloud affects-server New: affects-server
            Maciej Swinarski (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Users showed in the @-mention results are controlled via the permission scheme associated with given project with the Browse Projects permission.

            More about permission scheme configuration: https://confluence.atlassian.com/jserverm/latest/managing-project-permissions-979403889.html

             

            Maciej Swinarski (Inactive) added a comment - Users showed in the @-mention results are controlled via the permission scheme associated with given project with the Browse Projects permission. More about permission scheme configuration: https://confluence.atlassian.com/jserverm/latest/managing-project-permissions-979403889.html  
            Maciej Swinarski (Inactive) made changes -
            Attachment New: Screenshot 2021-10-19 at 16.24.53.png [ 411801 ]
            Maciej Swinarski (Inactive) made changes -
            Resolution Original: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Gathering Interest [ 11772 ]
            Maciej Swinarski (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            UIS Original: 30 New: 3
            SET Analytics Bot made changes -
            UIS Original: 24 New: 30

              Unassigned Unassigned
              dnicholson David Nicholson (Inactive)
              Votes:
              175 Vote for this issue
              Watchers:
              121 Start watching this issue

                Created:
                Updated:
                Resolved: