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

[PR #2126] [MERGED] fix(migration): make migration from Microsoft Todo work for those with previously migrated wunderlist accounts #3953

New Issue
Closed
opened 2026-03-22 14:57:37 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 14:57:37 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/2126
Author: @MEDumont
Created: 1/20/2026
Status: ✅ Merged
Merged: 2/17/2026
Merged by: @kolaente

Base: main ← Head: feature/fix-mstodo-graph-list-query

📝 Commits (1)

  • bd5b3a9 Fixed issue where the list query for Microsoft Todo import would query a paginated endpoint without using the next link. This endpoint also does not work for migrated accounts, such as those migrated over from Wunderlist. The delta endpoint handles this and returns all lists.

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 pkg/modules/migration/microsoft-todo/microsoft_todo.go (+1 -1)

📄 Description

Fixed issue where the list query for Microsoft Todo import would query a paginated endpoint without using the nextLink.
This endpoint also does not work for migrated accounts, such as those migrated over from Wunderlist. The delta endpoint handles this and returns all lists.

  • The Microsoft Graph API's /me/todo/lists endpoint only gets all lists that were originally created using the microsoft todo storage api. If the list was created as a result of migration (such as the Wunderlist migrations), then only newly created lists in the Microsoft Todo app will appear in the query.
  • In addition, this graph endpoint can reach a predefined limit and then resorts to pagination. If the "nextLink" is not handled in the code, then not all lists will be fetched.
  • The "/delta" endpoint is not paginated and will always get all lists, regardless of source. This will fix my issue and likely make it migrate easier for people with large numbers of lists.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-vikunja/vikunja/pull/2126 **Author:** [@MEDumont](https://github.com/MEDumont) **Created:** 1/20/2026 **Status:** ✅ Merged **Merged:** 2/17/2026 **Merged by:** [@kolaente](https://github.com/kolaente) **Base:** `main` ← **Head:** `feature/fix-mstodo-graph-list-query` --- ### 📝 Commits (1) - [`bd5b3a9`](https://github.com/go-vikunja/vikunja/commit/bd5b3a9b2e72f7a0b139beea577adbafd0e34071) Fixed issue where the list query for Microsoft Todo import would query a paginated endpoint without using the next link. This endpoint also does not work for migrated accounts, such as those migrated over from Wunderlist. The delta endpoint handles this and returns all lists. ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `pkg/modules/migration/microsoft-todo/microsoft_todo.go` (+1 -1) </details> ### 📄 Description Fixed issue where the list query for Microsoft Todo import would query a paginated endpoint without using the nextLink. This endpoint also does not work for migrated accounts, such as those migrated over from Wunderlist. The delta endpoint handles this and returns all lists. - The Microsoft Graph API's /me/todo/lists endpoint only gets all lists that were originally created using the microsoft todo storage api. If the list was created as a result of migration (such as the Wunderlist migrations), then only newly created lists in the Microsoft Todo app will appear in the query. - In addition, this graph endpoint can reach a predefined limit and then resorts to pagination. If the "nextLink" is not handled in the code, then not all lists will be fetched. - The "/delta" endpoint is not paginated and will always get all lists, regardless of source. This will fix my issue and likely make it migrate easier for people with large numbers of lists. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-22 14:57:37 -05:00
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 pull-request
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#3953
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?