Audit Log / Comments #111

Closed
opened 2025-04-07 23:00:52 +00:00 by Quaternions · 2 comments
Owner

The audit log contains information about who performed which actions on the submission or mapfix, such as who accepted, who uploaded, who changed the DisplayName, etc.

Frontend:
The audit log should function similarly to the timeline objects you see in gitea issues and pull requests.

Backend:

  • GET /api/submissions/[submissionId]/audit-events?Page=1&Limit=10
  • POST /api/submissions/[submissionId]/comment
  • GET /api/mapfixes/[mapfixId]/audit-events?Page=1&Limit=10
  • POST /api/mapfixes/[mapfixId]/comment
The audit log contains information about who performed which actions on the submission or mapfix, such as who accepted, who uploaded, who changed the DisplayName, etc. Frontend: The audit log should function similarly to the timeline objects you see in gitea issues and pull requests. Backend: - ~~GET `/api/submissions/[submissionId]/audit-events?Page=1&Limit=10`~~ - ~~POST `/api/submissions/[submissionId]/comment`~~ - ~~GET `/api/mapfixes/[mapfixId]/audit-events?Page=1&Limit=10`~~ - ~~POST `/api/mapfixes/[mapfixId]/comment`~~
Quaternions added the frontendbackend labels 2025-04-07 23:00:52 +00:00
Quaternions removed the backend label 2025-04-08 20:00:06 +00:00
Author
Owner

Implemented backend in #113.

Implemented backend in #113.
Author
Owner

Implemented frontend in #127 (it's super bad) by hijacking comments

Implemented frontend in #127 (it's super bad) by hijacking comments
Quaternions added this to the 1.0 Release milestone 2025-04-12 02:06:43 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StrafesNET/maps-service#111