-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Cases] Attachments cases activity item #152088
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/response-ops-cases (Feature:Cases) |
What will happen to the user action when you press "Delete" from the eclipse? |
I didn't elaborate much yet because I'm not sure this should be available in this view. Off the top of my head, I'd say disable the buttons in this item and add a new one with |
Tracking which files are deleted to disable the buttons will put an unnecessary (at least for the MVP) burden on Cases. What about having the actions only on the modal? It will be easier because when you click to see the file the previewer will get a 404 and we can show a not found view. Adding a new "User deleted attachment" user action sounds good to me. |
Fixes #152088 ## Summary Users are now able to see file activity in the case detail view. - Image files have a different icon and a clickable file name to preview - Other files have a standard "document" icon and the name is not clickable - The file can be downloaded by clicking the download icon <img width="1456" alt="Screenshot 2023-03-29 at 17 31 06" src="https://user-images.githubusercontent.com/1533137/228590244-c924bf2a-c5ac-47a0-ac1e-438cd089361b.png"> If the file has invalid metadata (not likely) we display the activity item below: <img width="808" alt="Screenshot 2023-03-29 at 17 36 25" src="https://user-images.githubusercontent.com/1533137/228591686-0bdf4077-ddbf-4da1-9d23-67c02e969c2c.png">
Subtask of #151595
Summary
Users should be able to see attachment activity in the case detail view.
Requirements
Copy reference link
buttonThe text was updated successfully, but these errors were encountered: