Update - new issue created here: JRACLOUD-82036 – We do not warn users that Moving issue to different project doesn't update assignee regardless of target project's permissions

Upon reflection, though I think this ticket was created in error I do think it should exist in another form: We need to explicitly highlight at some point in the Move process that this is the expected behaviour. I will reopen and update this ticket accordingly.

Apologies 823134ca6b95 - I meant to leave a clarification when I opened and re-closed this bug and then forgot to do so.

Previously this ticket was closed in 2019 with the Resolution "Fixed" which I believe is misleading as the behaviour remains as described.

Based on the research I have done, this functionality never existed in Jira Cloud. This ticket was cloned from the Jira Server one in error. A user's assignability (i.e. whether or not they have the Assignable project permission) at the time of assignment and that's it.

Can I confirm, are you seeking this feature in Jira Cloud or Jira Server?

Not a bug!!??

This issue is affecting us in cloud JST-920471

It is clearly not fixed.

This undermines our permissions configuration significantly and is a major impact if not fixed.

Please reopen and resolve it

.

This is still happening on Cloud and I'm not sure why this was closed. This is a big issue for my company currently as there doesn't seem to be a workaround.

Yeah, this is funny (not).

First of all, this is a regression. This means you broke it in the first place.

Then you let the bug report unassigned for about two years, all that happened in-between certainly didn't make the fix any easier.

Now we're told this is difficult to fix. Well....

Jacek that really is not an acceptable update. This is core functionality that broke in Version 7. When moving issues from one project to another if the current assignee does not have assignable rights on that project it needs to assign to the default assignee (project lead) for that project.

Dear watchers and voters,

Atlassian bugfix team investigated the issue and the work required to implement a proper fix to the problem is not as simple as leaving a blank assignee. Blanking assignee could be actually treated as another bug. 

We want to fix the problem correctly in all places and that means non trivial changes which require user experience expert and product manager input.

The issue is on our backlog but please keep voting as that increases its importance. 

Thanks,
Jacek Jaroczynski
JIRA Bugmaster
[Atlassian]

+1 concerning the previous comment. Oh and as a sidenote:
In project components you can assign a component lead and make him/her the default assignee in the dropdown next to the component lead field, although they may not have the permissions to actually be an assignee. Considering how broken this entire thing is already, I believe this comes as no surprise to anyone.