[$50]Tracks filter does not work for Open for Review bucket

[SathyaJayabal]

Tracks filter does not work for Open for Review bucket in challenge listings.

cc @lakshmiathreya @sushilshinde

[crazyk07]

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

This is an automated message for crazyk via Topcoder X

[crazyk07]

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

This is an automated message for crazyk via Topcoder X

[luizrrodrigues]

@sushilshinde PR's ready ☝️

[luizrrodrigues]

@sushilshinde PR updated.

[SathyaJayabal]

@luizrrodrigues , the appium challenges must be categorised as Development challenges.
here is the mapping document on how to map v4 challenges to v5 tracks.
https://docs.google.com/spreadsheets/d/1ltADd47U9aIP7M7YUyAhHUbLJgUHszvNo0sIYaiDr_A/edit?usp=sharing

Legacy challenges with subtracks "BUG_HUNT" ,"TEST_SUITES", "TEST_SCENARIOS" and "TESTING_COMPETITION" are mapped to the QA track. You do not map the challenges to the qa tracks based on technology tags.

[luizrrodrigues]

@SathyaJayabal Checking...

[luizrrodrigues]

@SathyaJayabal The review opportunities still have v4 API in challenges details.

In V4 API we look for QA in tags to check if is a QA is present.

So I see these are learning challenges, if not a QA track, so maybe QA tag was wrong added?

[SathyaJayabal]

@luizrrodrigues , Let's discuss this with @sushilshinde on Monday

[SathyaJayabal]

@luizrrodrigues , in V4 we did not have QA as a separate track.

All other buckets use V5 while Open for review still uses V4. We need to use the same mapping V5 uses for the other buckets, so that it is consistent. So for example for the above challenge, even though it is tagged with QA, it will still show up under develop track (in the other other buckets). Only challenges with subtrack "BUG_HUNT" ,"TEST_SUITES", "TEST_SCENARIOS" and "TESTING_COMPETITION" are mapped to the QA track in V5. We must follow the same for Open for review bucket, so that we dont have same challenge in different tracks in different buckets.

[SathyaJayabal]

verified on staging

[SathyaJayabal]

verified on staging (develop branch)

[SathyaJayabal]

verified on prod

[crazyk07]

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

This is an automated message for crazyk via Topcoder X