number of submissions tab only display for PAST challenges?

[iversonLv]

Steps to Reproduce

• Login as a valid user

• Go to http://community-app.topcoder.com/challenges/30058983/?type=develop
  (check live website: http://community-app.topcoder.com/challenges/30058983/?type=develop)

Actual Result(s)

• There is no submission tab display for ongoing challenge
  but display for past challenge (e.g. http://community-app.topcoder.com/challenges/30059069/?type=develop)

Expected Result(s)

• No matter what phases challenge, should display submission tab
  Is it new feature for topcoder website?

Environment

• Device(s): Desktop PC
• Operating System: Windows 10 64bit
• Browser(s): Version 60.0.3112.113 (Official Build) (64-bit)

Image/Video/JS Log/Console Log (If not attached here, Please check the comments section)

[birdofpreyru]

@ajefts Here I see an inconsistency in the backend, at least in case of active F2F challenges:

• numSubmissions field in v3 api response counts all submissions (including those that have not been reviewed yet);
• submissions array in v2 response seems to include only those submissions that have been reviewed already.

These should be update to behave consistently, depending on whether we want to show / hide details about submissions that have not been reviewed yet.

Otherwise, to make submission tab consistent for active challenges, I'll have to fallback to v2 api completely (now the number of submissions is taken from v3, and submission details from v2).

[ajefts]

@birdofpreyru We should be showing the full count of submissions regardless of if they have been reviewed or not yet. I checked a couple challenges on prod and v3 seems like it's right. Do you see a current challenge that has a discrepancy?

[birdofpreyru]

@ajefts Yes, e.g. https://community-app.topcoder.com/challenges/30059106

[birdofpreyru]

UPD: The issue is not visible anymore in prod, as it was leveraged with data from v2 api, but the api issue, preventing the correct fix with only v3 api, is still there.

[nithyaasworld]

Its not an issue anymore. Hence closing this.