fix(PM-6415): expose My Projects filter to talent managers - #2401
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the UI portion of PM-6415.
Work's project list explicitly exposes the My Projects membership filter to both Talent Manager role variants. Toggling it preserves the other filters and resets pagination through the existing memberOnly query flow; clearing it restores all projects visible under the service policy.
Companion service PR: topcoder-platform/projects-api-v6#47. Configure
INTERNAL_BILLING_ACCOUNT_IDSin that service to exclude internal projects from Talent Manager access.Validation:
yarn lint; project filter/list suites passed (3 tests); production build passed withNODE_OPTIONS=--max-old-space-size=8192. Updated the project-list test's outdated constants mock so the suite exercises the current permission helpers.