Issue Summary

In our document Preparing for Jira 9.11, there is a following description regarding the user mentions.

We can use the user mentions in the description field or the comment comment field when we edit multiple issues by using "Bulk edit" function. However, when issues belong to different projects with different permission scheme, only some of users are suggested by the picker, and those suggested mention can be added to selected issues regardless the "Browse Projects" permission.

Steps to Reproduce

1. Create software projects P1, P2 and P3
2. Create non-administrative users user1, user2. and user3
3. Create permission schemes PS1, PS2 and PS3 with the following settings
   1. PS1: Grant "Browse Projects" only to jira-administrators and user1
   2. PS2: Grant "Browse Projects" only to jira-administrators and user2
   3. PS3: Grant "Browse Projects" only to jira-administrators and user3
4. Assign the permission scheme PS1 to the project P1, PS2 to P2, and PS3 to P3 respectively
5. Create "Bug" type issues in P1, P2 and P3 respectively
6. Navigate to [Issues] > [Search for issues], then run with the following JQL. Three bug issues will be displayed

   project in (P1, P2, P3) and type = bug
   

7. Navigate [⚙️Tools] > [ Bulk change: all 3 issues(s)]
8. Select all issues on the bulk operation step 1
9. Select "Edit Issues" on the bulk operation step 2
10. On the bulk operation step 3, select "Change Description" and type "@us" into the description field. Check the suggested user in the picker popup
11. Select "user1" in the picker popup to insert the mention into the description, then finish editing
12. Click [Confirm] button on the bulk operation step 4
13. Check the description on each issues in P1, P2 and P3

Expected Results

• Regarding the mention suggestion, the expected result is unknown
• The user mention should not be added to issues which the mentioned user doesn't have "Browse projects" permission

Actual Results

• When "@us" is typed, the only "user1" is suggested by the picker
• The mention for "user1" is added not only to the description of the issue in P1, but also to issues in P2 and P3 which "user1" doesn't have "Browse projects" permission

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.