And suddenly, more than 5 years later, nothing happend. Problem still existing.

It looks like it is still not checked if the reporter has actual permissions (browse) in the destination projet.
It seems to suffice that the currently logged in user can create an issue in the destination project.

reiss.snooks1831337561, I'm not sure I understand your comment correctly. The problem has been fixed in versions 7.3.2 and newer; permissions are checked when moving issues. Are you saying that you are still experiencing the problem? I don't know what excuse you are referring to.

If there's anything unclear in the description or how the issue has been resolved please provide me with more details and I'll update it to make everything clear.

I've just been directed to this after logging a fresh issue with JSD, only to see that this is already marked as resolved with a terrible excuse for why.

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.

What does it take to get this prioritized? Restoring prior functionality that broke as the result of an upgrade should be prioritized over new enhancements.

Hi guys,

This problem has an outstanding impact on our JIRA usage. We have 200+ projects, and we rely on having issue assigned to a default assignee when it is moved between projects. We did not have this problem before upgrading from 6.3.8 to 7.1.1. I had to come up with a solution very quickly, so I managed to write a script that is a workaround for this problem. Prerequisite is that you have ScriptRunner for JIRA installed in your JIRA instance.

Please find attached onIssueMove.groovy script that has to be installed as a listener for ISSUE MOVED event. I hope this helps. The script is compatible with 7.x API.

Regards,
Milovan