Files
vikunja/pkg/modules/migration/ticktick/testdata_ticktick_invalid_numbers.csv
Tink bot ebb89ba4f3 fix(migration): tolerate non-numeric values in TickTick CSV exports
TickTick exports could contain non-numeric values in columns Vikunja
parses as integers (Priority, taskId, parentId). gocsv's strconv.ParseInt
then failed, aborting the entire import and surfacing as an internal
server error reported to Sentry (e.g. parsing "p1": invalid syntax).

Numeric ID columns now fall back to 0 for unparseable values instead of
failing the import. The Priority column, which was previously parsed but
never carried over to the imported task, is now mapped onto the task and
accepts both the plain numeric form (0, 1, 3, 5) and the "pN" form
(p1, p2, p3).

Closes #2822
2026-06-01 10:09:58 +00:00

774 B

1Date: 2026-02-27+0000
2Version: 7.1
3Status: 0 Normal 1 Completed 2 Archived
4Folder NameList NameTitleKindTagsContentIs Check listStart DateDue DateReminderRepeatPriorityStatusCreated TimeCompleted TimeOrderTimezoneIs All DayIs FloatingColumn NameColumn OrderView ModetaskIdparentId
5WorkProject BetaTask with non-numeric priorityTEXTA task whose priority column is p1Np102026-02-15 09:30:00-1099511627776Europe/Berlinfalselist1
6WorkProject BetaTask with non-numeric idsTEXTA task with garbage in the id columnsN002026-02-10 08:00:000Europe/Berlinfalsefalselistabcxyz