[$50] Behaviour when a ticket needs to be reassigned

[callmekatootie]

@afrisalyp - Can you take a look at this one please? If I remember right, this was due to the challenge API not working properly with unassigning the first user.

• User A assigned themselves to a ticket. They updated the labels as needed
• User A is not responsive. CoPilot wishes to remove User A. Another user, user B has expressed interest in taking up the ticket

If CoPilot removes user A and assigns (in the same step) user B, I find that TCX will assign and then unassign user B.

Note: It does not unassign user A

To actually assign user B, I need to remove the label tcx_assigned, set tcx_openforpickup and then assign user B. TCX finally accepts user B as the new assignee.

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

[callmekatootie]

Reference ticket https://www.topcoder.com/challenges/30119420 for topcoder-platform/resources-api#15 (comment)

[jmgasper]

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

This is an automated message for ghostar via Topcoder X

[jmgasper]

Contest https://www.topcoder.com/challenges/30119815 has been updated - it has been assigned to afrisalyp.

This is an automated message for ghostar via Topcoder X

[afrisalyp]

@jmgasper

I'm not able to create a challenge in the dev environment.

    Error: 'Failed to create challenge.', Details: {"status":400,"response":{"req":{"method":"POST","url":"http://api.topcoder-dev.com/v4/challenges","data":{"param":{"confidentialityType":"PUBLIC","technologies":[],"subTrack":"FIRST_2_FINISH","name":"My second issue","reviewType":"COMMUNITY","milestoneId":1,"detailedRequirements":"<p>sec</p>\n","submissionGuidelines":"Git issue link: https://github.com/telaga/topcoder-x-test-play/issues/3","registrationStartsAt":"2020-03-18T04:11:09.242Z","registrationEndsAt":"2020-03-23T04:11:09.242Z","submissionEndsAt":"2020-03-23T04:11:09.242Z","platforms":[],"finalDeliverableTypes":[],"prizes":[10],"projectId":7377,"task":true}},"headers":{"user-agent":"node-superagent/3.7.0","content-type":"application/json"}},"header":{"date":"Wed, 18 Mar 2020 04:11:10 GMT","content-type":"application/json","content-length":"160","connection":"close","server":"nginx","access-control-allow-headers":"Authorization,Content-Type,Accept,Origin,User-Agent,DNT,Cache-Control,X-Mx-ReqToken,Keep-Alive,X-Requested-With,If-Modified-Since","access-control-allow-credentials":"true","access-control-allow-methods":"GET, POST, OPTIONS, DELETE, PUT, PATCH"},"status":400,"text":"{\"id\":\"733ed472:170d302c354:7eae\",\"result\":{\"success\":true,\"status\":400,\"metadata\":null,\"content\":\"javax.ejb.EJBTransactionRolledbackException\"},\"version\":\"v3\"}"}}

I need the dev env to reproduce the issue and test the fixes.
So can you please help me to take a look at the dev challenge API to see if there's some wrong there?

[afrisalyp]

@jmgasper

I'm able to use the dev env by using the old token mechanism to test this issue fixes.
It's ready for review. Thanks.

[jmgasper]

Payment task has been updated: https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30119815

This is an automated message for ghostar via Topcoder X