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

Deleted items and collections should be logged with their name, not ID #3909

Closed
1 task done
appstate-linux-automation opened this issue Mar 18, 2024 · 1 comment
Closed
1 task done
Labels

Comments

@appstate-linux-automation

Steps To Reproduce

If you delete any item or collection, it gets logged properly. But they log entry references an ID, and so if I want to know "who deleted this entry," I can never find out unless I knew its ID already.

Expected Result

The audit log should, for all event types, not only log the item/collection ID but also the "name" as it was at the time the even occurred.

Actual Result

Only the ID is logged, which makes it difficult to track down who deleted an item or collection.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.2.3

Environment

Self-Hosted

Environment Details

RHEL 9, Docker, vmware VM

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@sammbw
Copy link

sammbw commented Mar 18, 2024

Hi there,

Your issue appears to be describing the intended behavior of the software. If you want this to be changed, it would be a feature request.

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests like this one: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums (https://community.bitwarden.com/signup) and search to see if this request already exists. If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed.

Thanks!

@sammbw sammbw closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants