[$50] Cancelled challenge not accessible

[jmgasper]

Expected behavior

I would expect cancelled challenges (due to no submission, failed review, client request, etc...) to be accessible somewhere in Work Manager, especially if we need to repost something.

Actual behavior

As far as I can tell, cancelled challenges disappear from work manager and aren't accessible on Active, New, Draft, or Completed tabs for a project.

Steps to reproduce the problem

• Run a challenge from WM
• Cancel the challenge
• Challenge is no long able to be found in WM

[vikasrohit]

@maxceem lets add a new tab called Cancelled which would list all cancelled challenges.

[maxceem]

@vikasrohit I'm trying to reproduce this issue, but have some difficulties with canceling challenges.

I've canceled 3 challenges using OnlineReview:

I waited around 20 minutes, but they are still "draft" in V5, so it looks like status wasn't synced back from OR to v5. See all these challenges in OR are cancelled:
https://software.topcoder-dev.com/review/actions/ViewProjectDetails?pid=30057916
https://software.topcoder-dev.com/review/actions/ViewProjectDetails?pid=30057845
https://software.topcoder-dev.com/review/actions/ViewProjectDetails?pid=30057849

[vikasrohit]

You may be right @maxceem. I think forward sync only pulls active and completed challenges back to V5. We need @rootelement 's help here. @rootelement can you please confirm if the forward sync brings back the cancelled challenges to v5 or not?

[rootelement]

The v4 -> v5 sync:

1. Gets the challenges in legacy with a status of Active
2. Gets the challenges in v5 with a status of Active
3. Aggregates the legacy IDs and deduplicates them
4. Performs the sync

If you change a challenge status from anything but Active (ie Draft) to Canceled, it will not sync forward from legacy. I'm not sure how to fix this. It would be better if we had the means to cancel the challenge from WM, so it'd be canceled from the community app side right away then propagate back to legacy.

[vikasrohit]

Thanks for the detailed response @rootelement. Would it just take a simple PATCH call to v5 challenge api to cancel the challenge?

[rootelement]

Sorry I didn't see this. Yes, patching as canceled would work. We could also add it in WM as it currently is in OR, but I don't know if we need business rules around it (who can do it, when can you, when can't you)