possible regression in assignee user list

[Aaron Rodriguez]

Starting on 2025-04-22 I've been getting spammed with Jira notifications as users in my org accidentally assign tickets to me, then immediately reassign them to themselves.

What seems to be happening:

• user is on a Jira ticket page
• user clicks the assignee field
• a dropdown appears, with their name and an Assign to me label
• the app asynchronously loads the list of all users
• they try to click Assign to me
• the user list finishes loading and now my name is in the same place ("Aaron" is alphabetically first)
• they accidentally click my name

Was there a UI change recently that might have caused this? Can something be done about it? I'd rather not have to ask my org's Jira admin to create a dummy user named AAAAAA to prevent this.

[Richard Wright]

As someone who accidentally assigns tickets to the wrong person because of this, I'd also like a solution. Two ideas for UI changes on Gitlab's side:

1. Keep the list height static with my user or "assign to me" at the top, so the async resolution of fetching other users doesn't affect the position
2. Display my user/"assign to me" but don't automatically fetch users and either force me to search for someone or add a "different user" button that then loads the list.

[Aaron]

As a fellow Aaron, I feel your pain. 

Luckily I'm in a position where I am the only person that assigns myself issues to actually work, so if I see the notification that someone has assigned me to a ticket, I just ignore it. 

It does seem to have become worse lately, so something mat have changed.