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

When a document is imported in grouping, it does not appear in content #6379

Closed
nino-filigran opened this issue Mar 18, 2024 · 0 comments · Fixed by #6641
Closed

When a document is imported in grouping, it does not appear in content #6379

nino-filigran opened this issue Mar 18, 2024 · 0 comments · Fixed by #6641
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

@nino-filigran
Copy link

Description

When uploading a file in a grouping, this file does not appear in content (it's the only container type behaving this way).

Environment

Demo

Reproducible Steps

2 ways:

  1. From an existing grouping
    Go to grouping
    Open a grouping from the list
    Go to Content
    Upload a file (I tried with a PDF)
    Wait until you have a success message of upload
    Go to data: the file is there

  2. From a new grouping
    Go in grouping
    click on the +
    fill mandatory fileds (name + context)
    Provide a file to upload
    Click on create
    Go to the content page: it's empty
    Go to the data page: the doc is uploaded

Expected Output

Any uploaded file should be in both content and datz

Actual Output

The files for grouping are only in data

Additional information

file example:
[Report] ConnectWise ScreenConnect attacks deliver malware (2024-02-28 07_45).pdf

Screenshots (optional)

@nino-filigran nino-filigran added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 18, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.8 milestone Mar 20, 2024
@Jipegien Jipegien modified the milestones: Release 6.0.8, Release 6.0.9 Mar 20, 2024
@SamuelHassine SamuelHassine modified the milestones: Release 6.0.9, Release 6.0.10, Release 6.1.0 Apr 3, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Apr 12, 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.

4 participants