[$40]Registration not reflecting for some challenges.

[SathyaJayabal]

Example: User picachui is registered to the below challenge
https://beta-community-app.topcoder.com/challenges/184a4437-7ee0-4b30-a614-6850ea9f1b86
The challenge belongs to a wipro-all group the user is a member of.

The challenge shows up under my challenges in the listings page:

Actual: In challenge details page, the user is not shown under the registrants tab, and the register button is active. The number of registrants is correct though.
Expected: User must be listed under registrants tab and The register button must be "Unregister"

The api call "http://api.topcoder.com/v5/challenges?memberId=22778049" with user token returns the below challenge as expected. This is a front-end fix.

[crazyk07]

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

This is an automated message for crazyk via Topcoder X

[crazyk07]

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

This is an automated message for crazyk via Topcoder X

[srjr19]

@SathyaJayabal kindly provide a challenge and user for local setup else not possible to test groups. As per my knowledge of the projects, groups are assigned by Topcoder team. So kindly provide a test which could be run on test env, so I can use the same on local setup to find the issue.

[SathyaJayabal]

@simranb86
https://test-community-app.topcoder-dev.com/challenges/2a3460ef-fb04-4609-958a-e7aad41dd321?tab=registrants
dan_developer/dantopcoder123

[srjr19]

Thanks @SathyaJayabal - looking into it. One Request - can you please remove labels like Need clarification going ahead when information is provided, helps me filter quick than going through each assigned ticket to check?

[srjr19]

@SathyaJayabal can you please reverify this once, I do see it working fine on test env.

[srjr19]

Also tested locally,

But I do see there is network issue on your side. See the network icon with Red Cross on your snapshot. Can you try incognito mode or fresh browser window ?

[srjr19]

@sushilshinde what status we put here as QA need to reverify ? Should it be Ready FOR QA ?

[SathyaJayabal]

@simranb86 add the ready for qa label in case your fix is ready and doesn't require any further actions like merge or deployment

[SathyaJayabal]

@simranb86 , You are correct, this example on test works correctly. But I still have the issue with the original contest on beta, where the member handle is not present on the registrants table too.

This is not an issue with private group challenges. Let's put this on hold until registration is fixed and we can retest the original contest.

[SathyaJayabal]

Same challenge, two registrants, the register button behaviour is different for the two users

[SathyaJayabal]

@simranb86 , here is another example you can look at
https://beta-community-app.topcoder.com/challenges/0e19815e-fb7e-4a8c-bb52-6e5c6c101818?tab=registrants
user: customeruser/appirio123

note: this is not a groups issue as previously inferred.

[srjr19]

@SathyaJayabal let me check and get back on this soon.

[srjr19]

@SathyaJayabal sorry for the delay on this, will wind up this now in next few hrs.

[rootelement]

Please let me know if this is still an issue. I believe this was a data sync issue that does not exist anymore.

[SathyaJayabal]

@rootelement @simranb86 , I don't see this anymore

[crazyk07]

This ticket was not processed for payment. If you would like to process it for payment, please reopen it, add the tcx_FixAccepted label, and then close it again

This is an automated message for crazyk via Topcoder X

[srjr19]

@SathyaJayabal isn't Topcoder paying members when they spend time on tickets anymore? Even one more ticket I see which I wasn't able to replicate after providing fix which was merged to code base and QA said fix is not working and today saw it was closed, saying QA cannot replicate the issue anymore. Not sure what's going on ?

@sushilshinde had opened that ticket for pickup but there was no fix after my last fix which code was merged but never reverted but QA said it didn't make it work. Plz see last few notes on #4491

[SathyaJayabal]

@simranb86 , there has been a lot of fixes in the frontend, backend, m2m token usage and data sync and migration in the last couple of weeks, that could have fixed these issues. This specific issue was caused by data sync which is now resolved.
#4566 (comment).

When testing these issues earlier, it was reproducible and you can see the screenshots for that. But since they are no more reproducible, I need to close it.

Please talk to @sushilshinde about payment for time spent on these issues.

cc @lakshmiathreya