Why is the assignee dropdown choosing the reporter by default instead of unassigned?

[Susan Wands]

In JIRA the create is defaulting assignee to reporter. It selects and pre-fills the reporter in the assignee dropdown. All of my projects are set to default assignee, unassigned. I have no automations. I have no components that could be overriding it. I have not changed anything recently. It just started ignoring my default assignee all of the sudden. Now my reporters, who are not devs and will not be working on fixing the issue, are assigned tickets in my project.

[Susan Wands]

Seems like there was already a ticket created off of this question chain... https://community.atlassian.com/forums/Jira-questions/Should-NOT-automatically-set-assignee-as-reporter/qaq-p/3013183#M1123384

[Jaime Escribano]

Hi Susan! Welcome to the community!

Would you mind adding a little more detail to help identify the issue? 

Can you see the assignee changing after the work item has been created in the History tab at the bottom of the ticket? 

Regards!

[Nicolas Moreau]

Hi!

Same issue here on JIRA Cloud. For all projects, all work types, no automation.

Project settings :

Create issue window :

History of fresh issue :

Details of fresh issue :

Regards!

[Jaime Escribano]

Thank you for the detailed response!

From what I can see in the details, it's not exactly that the default assignee is not working properly,but rather that the default option displayed is automatically filled with the current user. 

I understand that the user "Automatic" is still available and that, in choosing it, the Assignee remains empty after creation?

Would you be so kind as to attempt this in an incognito page and verify if the problem persists?

If it doesn't, it's most likely a cookies problem. If it does, we may need to raise a bug at the support portal :)

[Adam Cameron]

We have the same issue (on Jira Cloud). Just tested in an incognito window; same result.

Our default assignee is "unassigned", and this has always worked fine in the past. This new behaviour seems to have started happening about two weeks ago, maybe? It's pretty recent, anyhow.

[Jaime Escribano]

Hi Adam, thanks for giving it a try 😊

This seems like a bug. Looking at the timeline it might have something to do with the new navigation Atlassian is currently rolling out See Jira's New Navigation! at Atlassian Community Events Boise

This seems like unexpected behaviour and so I would recommend opening a ticket to Atlassian Support -> Atlassian Support

Sorry I couldn't offer more assistance!