TickTick import reopens closed issues #2553

Closed
opened 2026-03-22 14:11:50 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @Marck on GitHub (Feb 22, 2026).

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

When using the TickTick import function, already closed issues are imported as open and overdue. I think it has something to do with the way the CSV is built. Probably the statuscode is not respected. When having hundreds of closed issues spanning multiple projects it is a thing to manually close them one by one.
Below CSV demonstrates this on the demo site (v1.1.0-107-1ccc8dce) and screenshot demonstrates it is imported as open.

Vikunja Version

v1.1.0 through v1.1.0-107-1ccc8dce

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots and files

test-import.csv

Image
Originally created by @Marck on GitHub (Feb 22, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description When using the TickTick import function, already closed issues are imported as open and overdue. I think it has something to do with the way the CSV is built. Probably the statuscode is not respected. When having hundreds of closed issues spanning multiple projects it is a thing to manually close them one by one. Below CSV demonstrates this on the demo site (v1.1.0-107-1ccc8dce) and screenshot demonstrates it is imported as open. ### Vikunja Version v1.1.0 through v1.1.0-107-1ccc8dce ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots and files [test-import.csv](https://github.com/user-attachments/files/25468883/test-import.csv) <img width="859" height="478" alt="Image" src="https://github.com/user-attachments/assets/eb9627b7-d21b-498a-bc39-1ba5702b1472" />
Author
Owner

@vikunja-bot-app[bot] commented on GitHub (Feb 23, 2026):

This issue has been fixed in 249b651, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Feb 23, 2026): This issue has been fixed in [`249b651`](https://api.github.com/repos/go-vikunja/vikunja/commits/249b651692dfe6ab1afd6097a380e0cc65b5519c), please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
Author
Owner

@Marck commented on GitHub (Feb 23, 2026):

Thanks a lot!

@Marck commented on GitHub (Feb 23, 2026): Thanks a lot!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2553