Skip to content

PM-5488: Keep active registered challenges in My Challenges - #7248

Merged
jmgasper merged 1 commit into
developfrom
PM-5488-2
Jul 31, 2026
Merged

PM-5488: Keep active registered challenges in My Challenges#7248
jmgasper merged 1 commit into
developfrom
PM-5488-2

Conversation

@jmgasper

Copy link
Copy Markdown
Collaborator

What was broken

PR #7243 prevented scheduled and later-phase challenges from appearing in the live list by requiring an open Submission phase for All, My Challenges, and the total count. QA found that registered members then lost their still-ACTIVE challenges from My Challenges as soon as submission closed and review began.

Root cause

The public-list phase filter was also applied to the member-scoped My Challenges request. That request already uses memberId to identify the member's registered challenges, so currentPhaseName over-restricted the results.

What was changed

Removed the Submission phase constraint only from My Challenges while retaining its ACTIVE status and memberId filters. Kept the Submission filters for All and the total count so scheduled and later-phase challenges remain excluded from the public live list.

Any added/updated tests

Updated the action regression test to require ACTIVE status and memberId for My Challenges and explicitly verify that currentPhaseName is omitted. Existing action tests continue to verify the Submission filter for All and the total count.

Validation completed successfully:

  • npm run jest -- __tests__/shared/actions/challenge-listing/index.js — 3 tests passed
  • npm run lint
  • npm run build
  • npm test — 151 test suites, 322 tests, and 141 snapshots passed

What was broken

The previous fix limited My Challenges to ACTIVE challenges with an open Submission phase. Registered members therefore lost challenges once submission closed even though the challenge remained ACTIVE for review.

Root cause

The public-list phase filter added in PR #7243 was also applied to the member-scoped My Challenges request. The existing memberId filter already identifies registered challenges, so currentPhaseName over-restricted the results.

What was changed

Removed the Submission phase constraint only from My Challenges. Kept the ACTIVE status and memberId filters, and retained the Submission filters for All and the total count so scheduled and later-phase challenges remain excluded from the public live list.

Any added/updated tests

Updated the action regression test to require ACTIVE status and memberId while explicitly verifying that currentPhaseName is omitted. The existing All and total-count tests continue to cover their Submission filters.
@jmgasper
jmgasper requested a review from kkartunov as a code owner July 31, 2026 03:00
@jmgasper
jmgasper merged commit 8d9fb2d into develop Jul 31, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant