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

Impossible to share Note with Organization #10030

Closed
Lhorus6 opened this issue Feb 21, 2025 · 1 comment
Closed

Impossible to share Note with Organization #10030

Lhorus6 opened this issue Feb 21, 2025 · 1 comment
Assignees
Labels
bug use for describing something not working as expected regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Lhorus6
Copy link

Lhorus6 commented Feb 21, 2025

Description

The button to share Notes with Organizations is grayed out.

Image

NB: If a user who is not part of the main organization writes a Note, it is shared with these Organizations as expected. However, the button remains grayed out and in addition we cannot remove the Organizations affixed

Image

Environment

OCTI 6.5.2

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a Note with an admin (i.e. "bypass all capability")
  2. Try to share it with an Organization
    -> You can't, the button is grayed out
@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 21, 2025
@nino-filigran
Copy link

I've reproduced. @Lhorus6 as a workaround, you can use mass operations, it works.
The fix is to enable the CTA if the user has the right.

@nino-filigran nino-filigran added regression Label to identify the bug as a regression of previously working feature and removed needs triage use to identify issue needing triage from Filigran Product team labels Feb 21, 2025
@romain-filigran romain-filigran added this to the Bugs backlog milestone Feb 21, 2025
@SarahBocognano SarahBocognano self-assigned this Feb 24, 2025
@SarahBocognano SarahBocognano added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 24, 2025
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 regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

5 participants