Tasks moved to another project lose their history
in progress
taskade_kdb01
I have an archive project where tasks are moved as they are completed. I was doing some analysis today and discovered that the task is essentially recreated, erasing the original create and completed date, but doesn't change the status which just furthers the confusion because now it shows hundreds of tasks marked completed, but with no completed datetime.
That means I've lost a lot of historical data which was the purpose of requesting the created/completed datetimes in the first place years ago. A task being moved to a different project shouldn't erase that history. It should just update the modified date.
Between this and not being able to export the data to a csv in the first place, something that is provided by a competitor I'm researching, it may be what drives me to switch.
Log In
John at Taskade
This is a genuinely important issue — task history should follow the task wherever it goes, not get wiped on a move. Losing the original creation timestamp and completion date makes archival and audit workflows unreliable, which defeats the purpose of having an archive project at all.
We have logged this as a priority bug. While we work on preserving full history across project moves, one interim workaround is duplicating the task with its history intact before moving (the original stays in place with its timeline). That said, this should not require a workaround — moving a task should be a non-destructive operation. We will share an update here as soon as the fix lands. Thank you for catching this and providing such a clear reproduction scenario.
John at Taskade
Update: We're actively working on this!
This is in development and your votes helped us prioritize it.While you wait, check out what's new:
- **Taskade Genesis** — generate AI-powered apps, agents, and workflows
- **Community Hub** — 1000+ free templates and apps
Follow our progress: Changelog | Product Updates
Thanks for your patience and for helping shape Taskade!
John at Taskade
Update: We're actively working on this!
This is in development and tracked on our roadmap. Your votes helped prioritize it.
Check out what's new:
- Taskade Genesis — generate AI apps, agents, and workflows
- Community Hub — 1000+ free templates
Follow our progress: Changelog | Product Updates
John at Taskade
marked this post as
in progress
Update:
Known issue — task history (comments, status changes) should persist when moved. We're fixing this.In the meantime, explore what's new:
→ https://taskade.com/create — build apps and workflows with AI
→ https://taskade.com/community — 1000+ free templates
Follow our progress: https://taskade.com/changelog
j
jiawei.kek
hi there, thanks for the feedback.
i think tasks are created in reference to the project - which might be a technical limitation as to why things are not carried over.
i am curious though, as to why you prefer an entire project to store completed tasks, instead of moving tasks into a different block instead?
noted on the feature to export data into csv. i'll add your vote to the exisiting post https://www.taskade.com/feedback/feature-requests/p/export-to-csv-or-excel
taskade_kdb01
jiawei.kek 2 reasons: 1) It tends to get slowed down as the number of tasks increases, which is in the order of 1000's for me after several years. And 2) I tend to use the board view and it becomes cluttered as lists are completed and there isn't a way to mark a list as "complete", so it's also easier to archive off.
j
jiawei.kek
taskade_kdb01: Hello, apologies for the delayed reply. What "history" are you looking to be carried over?
As for current workarounds you can try, you could have an automation to move completed tasks to a new block (or board) if you'd like, so all completed tasks go there. Or sort the project to filter out completed tasks (to help with loading)