+1 this is a big UX improvement.

working with Jira should invlove less clicks and less editing for basic functionalities. We can do drag and drop for the EPIC/Release, but not for team. would be great if this is available. 

This feature would be great, we have several customers asking for it!

The "assign by drag and drops" can be already achieved, but in the 3rd-party BigPicture plugin for JIRA. the Resources screen is precisely this.

As a user of an agile board having asignee swimlanes i am not able to assign a ticket to myself. What follows is nothing but a usability nightmare (as described before).

Why is there no planned date to fix this issue? When can we expect an answer in this issue? What has to be done to prioritize this problem?

I'm surprised, that Atlassian says that they see it as an vaild feature request (after 2 years) and still (after 2 more years) still nothing happens...

You used to be able to do this in older (classic board) versions of JIRA I'm surprised the functionality was removed as we used this feature all the time. It used to be that we could drag it from one persons swimlane to the "unassigned" swimlane, we'd usually pull in a few bugs/stories into the unassigned for every sprint for the team to pick up in case they got blocked on one of their assigned tasks, then we'd drag and drop an unblocked story from unassigned into their queue.

This used to be a simple drag and drop, now we have to:
1) click on the ticket
2) click "a"
3) find the person in the drop down,
4) click assign
5) in some instances refresh the board

Many thanks for reporting this issue. We see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

Regards,
JIRA Agile Team

If you should implement this, please implement it in a way so that it is not restricted to setting the assignee (see GHS-4518). Having the scrum master set the assignee is IMHO very bad practice and should not be encouraged by dedicated tool support for this.

So an issue is currently assigned to "Bob" and shows up in Bob's swimlane. We want to re-assign the issue to "Jane". I want to simply drag the issue from Bob's swimlane to Jane's.

A very powerful and more flexible implementation of this would be to add a field to the swimlane definitions that set variables to administrator defined values. i.e. the "Bob" swimlane definition would have "assignee=bob" and the "Jane" swimlane would have "assignee=jane".

This way I could use query based swimlanes and define what happens when I move issues between swimlanes (something as simple as changing the assignee, or more complicated, like setting assignee, fixVersion, ...)