Currently, the logs collection includes two different fields, createdBy and userId, for user identification within the meta field. This inconsistency complicates queries for logs associated with specific users, as it requires checking both fields. We need to standardize the field name to userId across all log entries.
Expected Behavior
All entries in the logs collection should use a consistent field, userId, for user identification within the meta field. This will allow for uniform querying of logs by userId without having to handle cases where createdBy is used instead.
Current Behavior
Some documents in the logs collection use meta.createdBy while others use meta.userId. This inconsistency makes it more complex to fetch logs for a user, as queries need to account for both fields.
Screenshots
Reproducibility
[ ] This issue is reproducible
[x] This issue is not reproducible
Severity/Priority
[ ] Critical
[x] High
[ ] Medium
[ ] Low
Additional Information
Checklist
[x] I have read and followed the project's code of conduct.
[x] I have searched for similar issues before creating this one.
[x] I have provided all the necessary information to understand and reproduce the issue.
[x] I am willing to contribute to the resolution of this issue.
Issue Description
Currently, the logs collection includes two different fields, createdBy and userId, for user identification within the meta field. This inconsistency complicates queries for logs associated with specific users, as it requires checking both fields. We need to standardize the field name to userId across all log entries.
Expected Behavior
All entries in the logs collection should use a consistent field, userId, for user identification within the meta field. This will allow for uniform querying of logs by userId without having to handle cases where createdBy is used instead.
Current Behavior
Some documents in the logs collection use meta.createdBy while others use meta.userId. This inconsistency makes it more complex to fetch logs for a user, as queries need to account for both fields.
Screenshots
Reproducibility
Severity/Priority
Additional Information
Checklist