Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

app term should become unmapped if public composite term it was mapped to is changed back to private #198

Open
TravisWalterLBNL opened this issue May 20, 2021 · 0 comments
Assignees
Labels
bug Something isn't working medium priority

Comments

@TravisWalterLBNL
Copy link
Collaborator

If user1 creates a composite term and makes it public, then user2 maps an application term to that composite term, then user1 changes the composite term from public back to private, user2's application should become unmapped (since they should no longer have access to user1's private composite term). Currently, user2's application term stays mapped to user1's composite term even after user1 make the composite term private.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working medium priority
Projects
None yet
Development

No branches or pull requests

2 participants