You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
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
The text was updated successfully, but these errors were encountered:
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
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:
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
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)
The text was updated successfully, but these errors were encountered: