Unregister the member who is not assigned

[anonymousjaggu]

Currently, I was assigned to a task and then I was unassigned. I think I should be un-registered from the challenge as well, it's showing me the registrant of that task.
It shows that challenge in My Challenges, so I suggest to remove the un-assigned participant from the challenge.

For the Topcoder-X challenge

We need to validate and debug the flow above, using the v5 API. When users un-assign themselves from tickets, they should be removed as the submitter on the backing Topcoder challenge as well, ensuring that there is only one assignee / submitter on a challenge at all times. There should not be a way that there are more than one assignee / submitter. If there are multiple assignees on a Gitlab / Github ticket, we won't set any assignee on the Topcoder challenge and will post a message to the Gitlab / Github ticket that multiple assignees are not supported. This message should be working, but should be tested with the latest v5 changes.

[callmekatootie]

Probably related - #292

However, I am now stuck with both user A and user B as assignees in TCX - github shows only user B as the assignee...

This bit does not seem to have been fixed. The earlier member continues to be seen as a submitter for the challenge, even though they are no longer assigned

[callmekatootie]

Workable solution for now - To unassign the member, remove the Open For Pickup label and assign the member again. They get unassigned (I am assuming because the label is not set, so they cannot pick it up)

[jmgasper]

Contest https://www.topcoder.com/challenges/30161061 has been created for this ticket.

This is an automated message for ghostar via Topcoder X