github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-13 09:21:39 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #576] Implement Detailed Revision History for Tasks Including Status, Assignee, and Other Changes #6266

New Issue
Open
opened 2026-04-20 16:50:50 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 16:50:50 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/576

Original issue by devadattas on 2024-07-22T05:00:08.000Z

Description

It would be highly beneficial to have a detailed revision history for tasks within Vikunja. This history should capture various changes such as:

  • Status Change
  • Assignee Change
  • Priority Change
  • Due Date Change
  • Description Change
  • Any other relevant task attribute changes

This feature is especially crucial for repeating tasks where tracking the history of changes can provide better context and understanding of the task's evolution over time.

Use Cases:

  1. Audit Trail: Users can see who made changes and what those changes were, providing a clear audit trail.
  2. Collaboration: Teams can better understand the workflow and any adjustments made to the tasks.
  3. Error Tracking: Easily identify if a task was incorrectly modified and revert changes if needed.
  4. Repeating Tasks: For tasks that repeat over time, it’s crucial to see how each instance of the task has been modified.

Proposed Implementation:

  • Add a "History" tab within the task details view.
  • Log each change with a timestamp, the user who made the change, and the specific details of the change.
  • Allow filtering and sorting of the history log for better usability.

This enhancement would significantly improve task management and collaboration within Vikunja.

Vikunja Version

latest

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No response

Screenshots

No response

Original issue on Gitea

@kolaente commented on 2024-08-07T15:57:20.000Z:

An audit log is planned as part of Vikunja Enterprise: https://community.vikunja.io/t/vikunja-as-a-business/2345

We might implement some kind of task history for everyone else as well.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/576 _Original issue by devadattas on 2024-07-22T05:00:08.000Z_ ### Description It would be highly beneficial to have a detailed revision history for tasks within Vikunja. This history should capture various changes such as: - Status Change - Assignee Change - Priority Change - Due Date Change - Description Change - Any other relevant task attribute changes This feature is especially crucial for repeating tasks where tracking the history of changes can provide better context and understanding of the task's evolution over time. **Use Cases:** 1. **Audit Trail:** Users can see who made changes and what those changes were, providing a clear audit trail. 2. **Collaboration:** Teams can better understand the workflow and any adjustments made to the tasks. 3. **Error Tracking:** Easily identify if a task was incorrectly modified and revert changes if needed. 4. **Repeating Tasks:** For tasks that repeat over time, it’s crucial to see how each instance of the task has been modified. **Proposed Implementation:** - Add a "History" tab within the task details view. - Log each change with a timestamp, the user who made the change, and the specific details of the change. - Allow filtering and sorting of the history log for better usability. This enhancement would significantly improve task management and collaboration within Vikunja. ### Vikunja Version latest ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? _No response_ ### Screenshots _No response_ [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/2638) --- _**@kolaente** commented on 2024-08-07T15:57:20.000Z_: An audit log is planned as part of Vikunja Enterprise: https://community.vikunja.io/t/vikunja-as-a-business/2345 We might implement some kind of task history for everyone else as well.
GiteaMirror added the area/task-metadataarea/task-editor labels 2026-04-20 16:50:50 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/task-editor area/task-metadata
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6266
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?