private project mapping and validation permission checks team membership along with project allowed users#7049
Merged
ramyaragupathy merged 1 commit intostagingfrom Oct 15, 2025
Conversation
…hip along with project allowed users
|
nischalstha9
approved these changes
Oct 15, 2025
manjitapandey
approved these changes
Oct 15, 2025
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
4 participants
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.
What type of PR is this? (check all applicable)
Related Issue
Fixes #7048
Describe this PR
HOTFIX: For private projects, only project allowed users list was checked for permission which is mostly not assigned which resulted in user not allowed error. But apart from managers or project allowed users, the team members assigned to the project can also map/validate given the permission. This pr adds the check for team members for the private project.