Issue on milestone page should be assigned to me when I dropped it to ongoing list

This issue was introduced with Multiple Issue Assignee

@ClemMakesApps I prepared a regression spec https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11678. The issue should be fixed solely on FE side. You can use my MR if you want to.

How to reproduce:

1. Create a milestone with few unassigned issues

2. Go to the milestone page

3. Drag the issue from the first list to the seconds like shown on the image

4. Look at the browser console, you will see that AJAX request got 500 error.

The MR https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11678

mentioned in merge request !11637

Not really sure I understand what the issue is here

changed the description

@ClemMakesApps I added steps to reproduce

Confirmed

changed the description

mentioned in issue #32437 (closed)

unassigned @vsizov

@ClemMakesApps Have you reproduced it?

added Next Patch Release label

Have you reproduced it?

@vsizov, I was out on vacation and was speaking at a conference. Will try to find time to resolve this.

assigned to @MadLittleMods and unassigned @ClemMakesApps

It looks like the "Ongoing Issues (open and assigned)" column, lists any issues that are assigned to anyone (not just yourself). I assume we want to assign someone (yourself in this case) because we want to keep it in the "assigned" list on refresh.

I see two ajax requests go out but they both succeed with a 200

• PUT /foo/bar/issues/36
• PUT /foo/bar/milestones/4/sort_issues

---

I'll update the issue update request to add yourself as an assignee

added frontend label

mentioned in commit 4d74df25

mentioned in merge request !12076 (merged)

mentioned in commit dded02d1

closed via merge request !12076 (merged)

mentioned in commit bfddd9ca

mentioned in commit 25b9d8e5

mentioned in merge request !14785