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

done_at field is lost when moving a task to another project and back #614

New Issue
Closed
opened 2025-11-01 21:00:24 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-01 21:00:24 -05:00
Owner
Copy Link

Originally created by @Plong-Wasin on GitHub (Sep 11, 2025).

Description

When a task is moved from one project to another and then moved back to the original project, the done_at field (the timestamp indicating when the task was completed) disappears or is lost.

Expected behavior:

  • The done_at value should be preserved when moving tasks between projects, including when moving the task back to the original project.

Actual behavior:

  • After moving a task to a different project and then returning it to the original project, the done_at field is missing or reset.

Steps to reproduce:

  1. Mark a task as done, ensuring the done_at timestamp is present.
  2. Move the task from the original project to a different project.
  3. Move the same task back to the original project.
  4. Observe that the done_at field is no longer set on the task.

This issue may lead to inaccurate task status or history loss. Preserving the done_at field during project moves will ensure task completion data consistency.

Vikunja Version

v1.0.0-rc1-128-e5e0413b

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @Plong-Wasin on GitHub (Sep 11, 2025). ### Description When a task is moved from one project to another and then moved back to the original project, the `done_at` field (the timestamp indicating when the task was completed) disappears or is lost. Expected behavior: - The `done_at` value should be preserved when moving tasks between projects, including when moving the task back to the original project. Actual behavior: - After moving a task to a different project and then returning it to the original project, the `done_at` field is missing or reset. Steps to reproduce: 1. Mark a task as done, ensuring the `done_at` timestamp is present. 2. Move the task from the original project to a different project. 3. Move the same task back to the original project. 4. Observe that the `done_at` field is no longer set on the task. This issue may lead to inaccurate task status or history loss. Preserving the `done_at` field during project moves will ensure task completion data consistency. ### Vikunja Version v1.0.0-rc1-128-e5e0413b ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2025-11-01 21:00:25 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 11, 2025):

Fixed in https://github.com/go-vikunja/vikunja/pull/1470, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Sep 11, 2025): Fixed in https://github.com/go-vikunja/vikunja/pull/1470, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
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
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#614
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?