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

Ensure that notes / opinions are both respecting the RBAC "knowledge feedback" and other aspects #8227

Closed
SamuelHassine opened this issue Sep 2, 2024 · 0 comments · Fixed by #8885
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@SamuelHassine
Copy link
Member

SamuelHassine commented Sep 2, 2024

Description

Ensure that notes / opinions are both respecting the RBAC "Access collaborative knowledge" and other aspects:

  1. Ensure that a user with "Access collaborative knowledge" can always create notes / opinions
  2. Ensure that user is able to read / update its own notes / opinions
  3. Ensure that if user is part of an organization, the notes / opinions are shared with the organization
  4. Ensure that organization administrator can see / manage notes / opinions of the users part of his organization
@SamuelHassine SamuelHassine added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Sep 2, 2024
@romain-filigran romain-filigran added ingestion Linked to ingestion (manual, from file, feeds & queue) and removed needs triage use to identify issue needing triage from Filigran Product team labels Sep 3, 2024
@romain-filigran romain-filigran added this to the Bugs backlog milestone Sep 3, 2024
@SamuelHassine SamuelHassine changed the title Worker should retry on Request timed out Ensure that notes / opinions are both respecting the RBAC "knowledge feedback" and other aspects Sep 4, 2024
@SamuelHassine SamuelHassine removed the ingestion Linked to ingestion (manual, from file, feeds & queue) label Sep 4, 2024
@SamuelHassine SamuelHassine self-assigned this Sep 7, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Nov 2, 2024
@SamuelHassine SamuelHassine reopened this Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
2 participants