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 see a file uploaded if we are not part of the platform organization #5435

Closed
Lhorus6 opened this issue Jan 9, 2024 · 1 comment · Fixed by #5587
Closed
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)

Comments

@Lhorus6
Copy link

Lhorus6 commented Jan 9, 2024

Description

When I upload a file in the platform (from the global import panel or from a "Data" tab of an entity), the file isn't appear if I am not part of the platform organization.

Environment

OCTI 5.12.15

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Set up user A admin and part of Org A
  2. Set up user B normal user and part of Org B
  3. Set up Org A as platform organization
  4. Create a Report with User B and upload a file from the "Data" tab of the Report
  5. Try to see this file from User B (you can't), then from User A (you can)

The screenshot below illustrates this

Expected Output

I should see the file with User B

Screenshots

  • On the left, my view from User A part of the platform organization and admin
  • On the right, my view from User B (not admin), who create the report and upload the file

Screenshot 2024-01-09 092509

@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 Jan 9, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 9, 2024
@SamuelHassine SamuelHassine added this to the Release 5.12.17 milestone Jan 9, 2024
@SamuelHassine
Copy link
Member

@nino-filigran can you confirm this bug? If so, can you sync with @Kedae for a quick resolution?

@Kedae Kedae self-assigned this Jan 18, 2024
@Kedae Kedae linked a pull request Jan 18, 2024 that will close this issue
@Kedae Kedae added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 22, 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
Development

Successfully merging a pull request may close this issue.

5 participants