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

Fix project bug that prevents project members from confirming matches on project encounters #957

Open
goddesswarship opened this issue Dec 20, 2024 · 7 comments
Labels
bug something's broken!

Comments

@goddesswarship
Copy link
Contributor

goddesswarship commented Dec 20, 2024

Expected behavior
Adding users to a project gives them access to those project encounters and the ability to confirm matches on them

Current behavior
Users in a project can view the encounters in that project but are unable to confirm matches for those encounters without a collaboration in place from the encounter owner. Because collaborations allow view or edit access to all of a user's encounter data, this workaround isn't ideal for users who are working with sensitive data.

Community link
https://community.wildme.org/t/collaborations-on-specific-project-sites-only/4521

@goddesswarship goddesswarship added enhancement new or improvements on existing features question open investigation to define scope of issue labels Dec 20, 2024
@goddesswarship
Copy link
Contributor Author

Adding question tag so the details of the scope can be worked out.

@TanyaStere42
Copy link
Member

this can be done through projects. create a project and add the user to it

@goddesswarship
Copy link
Contributor Author

But the user can't confirm matches on the encounters in that project unless a collaboration exists between them

@TanyaStere42
Copy link
Member

haaa that might be a bug 😆 This is the weirdness between read, match, and edit that isn't always handled consistently.

The intention of projects was to grant read-and-match access to a subset of data that all users in the project can add to and manage

@goddesswarship
Copy link
Contributor Author

Oh, that's a relief then. If only because users find it annoying that they have to take this extra step to make their project management functional. I'll write a separate ticket for it later today unless you beat me to it.

@TanyaStere42
Copy link
Member

have at it :D Just rework this one?

@goddesswarship goddesswarship changed the title Ability to restrict which data is visible to a collaborator Fix project bug that prevents project members from confirming matches on project encounters Dec 20, 2024
@goddesswarship goddesswarship added bug something's broken! and removed enhancement new or improvements on existing features question open investigation to define scope of issue labels Dec 20, 2024
@goddesswarship
Copy link
Contributor Author

Ok, the ticket's been rewritten and and tagged as a bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something's broken!
Projects
None yet
Development

No branches or pull requests

2 participants