vikunja/vikunja
8
54
Fork 94
Code Issues 101 Pull Requests 31 Packages Releases 37 Activity

Implement Detailed Revision History for Tasks Including Status, Assignee, and Other Changes #2638

New Issue
Open
opened 2024-07-22 05:00:08 +00:00 by devadattas · 2 comments
devadattas commented 2024-07-22 05:00:08 +00:00
Contributor
Copy Link

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

### 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_
👍 1
devadattas added the
kind/bug
 label 2024-07-22 05:00:08 +00:00
konrad commented 2024-08-07 15:57:20 +00:00
Owner
Copy Link

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.

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.
👍 1
konrad added
kind/feature
 and removed
kind/bug
 labels 2024-12-13 16:36:50 +00:00
frederick added the
moved-to-github
 label 2025-04-01 11:08:53 +00:00
frederick commented 2025-04-01 11:08:53 +00:00
Member
Copy Link

As we're moving Vikunja to GitHub, this issue has been migrated to GitHub: https://github.com/go-vikunja/vikunja/issues/576

To learn more about why we're doing this, please check out the announcement.

As we're moving Vikunja to GitHub, this issue has been migrated to GitHub: https://github.com/go-vikunja/vikunja/issues/576 To learn more about why we're doing this, please check out the [announcement](https://vikunja.io/changelog/moving-to-github/).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
dependencies
duplicate
This issue or pull request already exists
help wanted
Need some help
invalid
Something is wrong
kind/bug
Something is not working
kind/feature
New feature
moved-to-github
needs reproduction
question
More information is needed
security
wontfix
This won't be fixed
No Label
kind/feature
moved-to-github
Milestone
No items
No Milestone
Assignees
Clear assignees
dpschen frederick konrad renovate shilch
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vikunja/vikunja#2638
No description provided.
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?