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

[GH-ISSUE #238] Integration microsoft to do list import function does not import #6001

New Issue
Closed
opened 2026-04-20 16:30:13 -05:00 by GiteaMirror · 17 comments
GiteaMirror commented 2026-04-20 16:30:13 -05:00
Owner
Copy Link

Originally created by @inuonly on GitHub (Mar 18, 2024).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/238

Description

The import option in menu leads to a page where microsoft to do list can be imported, once the process completes we are greeted with a successful message and are informed that it will happen in background and we will notify. Even after days we still dont se any list imported from microsoft to do. Same is applid to trello just to check but it still is not working. It never fails both methods microsoft to do and trello are completing successfully. But nothign is imported.

Vikunja Version

Version: v0.23.0

Browser and version

123.0.1 (64-bit)

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Vikunja Version :
image
Browser Version :
image

Steps :

  1. Import page options:
    image
  2. individual microsoft to do import page
    image
  3. microsoft login page
    image
  4. redirected back to result page in vikunja after logging in
    image
Originally created by @inuonly on GitHub (Mar 18, 2024). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/238 ### Description The import option in menu leads to a page where microsoft to do list can be imported, once the process completes we are greeted with a successful message and are informed that it will happen in background and we will notify. Even after days we still dont se any list imported from microsoft to do. Same is applid to trello just to check but it still is not working. It never fails both methods microsoft to do and trello are completing successfully. But nothign is imported. ### Vikunja Version Version: v0.23.0 ### Browser and version 123.0.1 (64-bit) ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots Vikunja Version : ![image](https://github.com/go-vikunja/vikunja/assets/26686197/a33d78e7-5398-4edd-962e-37e4ce8947e7) Browser Version : ![image](https://github.com/go-vikunja/vikunja/assets/26686197/6ee8074d-54bc-4ee3-bc5e-1310b731b237) Steps : 1. Import page options: ![image](https://github.com/go-vikunja/vikunja/assets/26686197/7a415dae-bdcf-4eaa-a016-8d181e3a0159) 2. individual microsoft to do import page ![image](https://github.com/go-vikunja/vikunja/assets/26686197/ff5a7379-a910-4042-ab30-dd945e093870) 3. microsoft login page ![image](https://github.com/go-vikunja/vikunja/assets/26686197/c6e064a3-cd63-4cf0-9bfc-9addce2e12db) 4. redirected back to result page in vikunja after logging in ![image](https://github.com/go-vikunja/vikunja/assets/26686197/b1ea2407-ca26-45c9-8708-8ab9416358b1)
GiteaMirror commented 2026-04-20 16:30:15 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 18, 2024):

What do you see in the logs?

<!-- gh-comment-id:2003284371 --> @kolaente commented on GitHub (Mar 18, 2024): What do you see in the logs?
GiteaMirror commented 2026-04-20 16:30:16 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Mar 18, 2024):

What do you see in the logs?
image

It shows something like this but even if I scroll I see no error message or anything specific to import or similar info or error message.

<!-- gh-comment-id:2003454172 --> @inuonly commented on GitHub (Mar 18, 2024): > What do you see in the logs? ![image](https://github.com/go-vikunja/vikunja/assets/26686197/d03375e6-356c-437f-8bbd-74f34c57317a) It shows something like this but even if I scroll I see no error message or anything specific to import or similar info or error message.
GiteaMirror commented 2026-04-20 16:30:16 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 19, 2024):

If you search the log for Error, do you see anything?

<!-- gh-comment-id:2005386350 --> @kolaente commented on GitHub (Mar 19, 2024): If you search the log for Error, do you see anything?
GiteaMirror commented 2026-04-20 16:30:17 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Mar 19, 2024):

If I search error , then there is 0 entries . If i search for microsoft then I get only this entry and I just now tried to import once to get this in logs.
image
Apart from this entry everythign else is just a 200 or 304 log in approximately 1000 lines of logs.

<!-- gh-comment-id:2005848307 --> @inuonly commented on GitHub (Mar 19, 2024): If I search error , then there is 0 entries . If i search for microsoft then I get only this entry and I just now tried to import once to get this in logs. ![image](https://github.com/go-vikunja/vikunja/assets/26686197/5fa00c7b-d674-4e7c-a50f-d6312123c873) Apart from this entry everythign else is just a 200 or 304 log in approximately 1000 lines of logs.
GiteaMirror commented 2026-04-20 16:30:18 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 19, 2024):

What is the log level?

<!-- gh-comment-id:2006666036 --> @kolaente commented on GitHub (Mar 19, 2024): What is the log level?
GiteaMirror commented 2026-04-20 16:30:19 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Mar 19, 2024):

I dont have any idea what level log is it, since I have not changed the config, it should be the default. Let me look into hot to manually changing the log level.

<!-- gh-comment-id:2007312238 --> @inuonly commented on GitHub (Mar 19, 2024): I dont have any idea what level log is it, since I have not changed the config, it should be the default. Let me look into hot to manually changing the log level.
GiteaMirror commented 2026-04-20 16:30:20 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Mar 19, 2024):

So by default the logs go to info level, as per instructions here - https://vikunja.io/docs/config-options/ . I went further and changed log level manually to debug and here is the screenshot . I restarted my vikunja instance but still there is no sign of error in logs and the import option completes with the same message that it was successful and will be carried in background. But nothign shows up related to any import from my microsoft to do account.
image
This is the log , after changing to debug level now.

<!-- gh-comment-id:2007358225 --> @inuonly commented on GitHub (Mar 19, 2024): So by default the logs go to info level, as per instructions here - https://vikunja.io/docs/config-options/ . I went further and changed log level manually to debug and here is the screenshot . I restarted my vikunja instance but still there is no sign of error in logs and the import option completes with the same message that it was successful and will be carried in background. But nothign shows up related to any import from my microsoft to do account. ![image](https://github.com/go-vikunja/vikunja/assets/26686197/b0a22d41-b209-4467-9104-574219c41ef4) This is the log , after changing to debug level now.
GiteaMirror commented 2026-04-20 16:30:21 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 20, 2024):

This is the log , after changing to debug level now.

This looks like the import did not actually start - did it tell you "you already did the import once, do you really want to do this again?" - in that case you need to confirm the import.
The debug log should give you plenty of information while the import is running, in your case it looks like it didn't start.

<!-- gh-comment-id:2009202853 --> @kolaente commented on GitHub (Mar 20, 2024): > This is the log , after changing to debug level now. This looks like the import did not actually start - did it tell you "you already did the import once, do you really want to do this again?" - in that case you need to confirm the import. The debug log should give you plenty of information while the import is running, in your case it looks like it didn't start.
GiteaMirror commented 2026-04-20 16:30:21 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Mar 20, 2024):

No it does not spill any such message for confirming to do again as you mentioned. The result is same means the screenshot in step 4 always appears. Logs only show same thing over and over again.

<!-- gh-comment-id:2009285639 --> @inuonly commented on GitHub (Mar 20, 2024): No it does not spill any such message for confirming to do again as you mentioned. The result is same means the screenshot in step 4 always appears. Logs only show same thing over and over again.
GiteaMirror commented 2026-04-20 16:30:22 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 20, 2024):

Okay, then that's the bug. I'll take a look.

<!-- gh-comment-id:2009305710 --> @kolaente commented on GitHub (Mar 20, 2024): Okay, then that's the bug. I'll take a look.
GiteaMirror commented 2026-04-20 16:30:25 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Mar 20, 2024):

If it helps, I am available on discord and also not deleting the instance I have just in case if it cannot be reproduced. Hope you find it.

<!-- gh-comment-id:2009458170 --> @inuonly commented on GitHub (Mar 20, 2024): If it helps, I am available on discord and also not deleting the instance I have just in case if it cannot be reproduced. Hope you find it.
GiteaMirror commented 2026-04-20 16:30:27 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 20, 2024):

I'm heading off on vacation tomorrow for a week, will ping you back after that when I find something.

<!-- gh-comment-id:2009511159 --> @kolaente commented on GitHub (Mar 20, 2024): I'm heading off on vacation tomorrow for a week, will ping you back after that when I find something.
GiteaMirror commented 2026-04-20 16:30:29 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 7, 2024):

The message not showing is fixed in 0b9ef27d04. Please check with the next unstable build (should be ready for deployment in ~45min, also on try).

<!-- gh-comment-id:2041468144 --> @kolaente commented on GitHub (Apr 7, 2024): The message not showing is fixed in https://github.com/go-vikunja/vikunja/commit/0b9ef27d04f388b86acad854ad118c870fead02a. Please check with the next unstable build (should be ready for deployment in ~45min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2026-04-20 16:30:30 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Apr 8, 2024):

Since I am running in docker environment, can I manually change those two lines in respective two files? ( 0b9ef27d04 one I think is optional being a comment); as I suppose these changes will take time to reach docker images. I am trying to find the location of these files in docker instance but not able to find the path to the MigrationHandler.vue file or am I doing this wrong way.

The message not showing is fixed in 0b9ef27. Please check with the next unstable build (should be ready for deployment in ~45min, also on try).

<!-- gh-comment-id:2042125612 --> @inuonly commented on GitHub (Apr 8, 2024): Since I am running in docker environment, can I manually change those two lines in respective two files? ( https://github.com/go-vikunja/vikunja/commit/0b9ef27d04f388b86acad854ad118c870fead02a one I think is optional being a comment); as I suppose these changes will take time to reach docker images. I am trying to find the location of these files in docker instance but not able to find the path to the MigrationHandler.vue file or am I doing this wrong way. > The message not showing is fixed in [0b9ef27](https://github.com/go-vikunja/vikunja/commit/0b9ef27d04f388b86acad854ad118c870fead02a). Please check with the next unstable build (should be ready for deployment in ~45min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2026-04-20 16:30:32 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 8, 2024):

as I suppose these changes will take time to reach docker images

The change is already in the latest unstable build. You can just use the :unstable tag for the docker image, pull and restart your stack and you should be good to go. Make a backup first! You can learn more about the different versions here.

I am trying to find the location of these files in docker instance but not able to find the path to the MigrationHandler.vue file or am I doing this wrong way.

You can't edit the file in the docker container because they only contain the final compiled binary with the frontend and api bundled, not the source files. If you still want to edit the files, you need to build Vikunja from sources manuall. In your case, it's a lot easier to just switch to unstable though.

<!-- gh-comment-id:2042259060 --> @kolaente commented on GitHub (Apr 8, 2024): > as I suppose these changes will take time to reach docker images The change is already in the latest unstable build. You can just use the `:unstable` tag for the docker image, pull and restart your stack and you should be good to go. Make a backup first! [You can learn more about the different versions here](https://vikunja.io/docs/versions/). > I am trying to find the location of these files in docker instance but not able to find the path to the MigrationHandler.vue file or am I doing this wrong way. You can't edit the file in the docker container because they only contain the final compiled binary with the frontend and api bundled, not the source files. If you still want to edit the files, you need to [build Vikunja from sources](https://vikunja.io/docs/build-from-sources/) manuall. In your case, it's a lot easier to just switch to unstable though.
GiteaMirror commented 2026-04-20 16:30:32 -05:00
Author
Owner
Copy Link

@inuonly commented on GitHub (Apr 9, 2024):

Hey thanks for the tip. just used unstable tag for docker image and now migration part works.
It went in the very first attempt. Also if I revisit, it warns me about duplicate entries possibility before confirming just like you asked earlier.
One question, do i need to keep using unstable or does these changes reflect in latest tag docker image after some time.
Thank you so much <3 .
I believe we could close this issue. Also hope your vacations went well. [forgor that] .

<!-- gh-comment-id:2045396504 --> @inuonly commented on GitHub (Apr 9, 2024): Hey thanks for the tip. just used `unstable` tag for docker image and now migration part works. It went in the very first attempt. Also if I revisit, it warns me about duplicate entries possibility before confirming just like you asked earlier. One question, do i need to keep using unstable or does these changes reflect in latest tag docker image after some time. Thank you so much <3 . I believe we could close this issue. Also hope your vacations went well. [forgor that] .
GiteaMirror commented 2026-04-20 16:30:33 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 9, 2024):

Unstable builds are built from the latest commit in the main branch. In irregular intervals a release is made from that and then the changes will be cut into a release. In your case, that means you can keep using unstable and then switch to the next release once that's out.

<!-- gh-comment-id:2045940930 --> @kolaente commented on GitHub (Apr 9, 2024): Unstable builds are built from the latest commit in the main branch. In irregular intervals a release is made from that and then the changes will be cut into a release. In your case, that means you can keep using unstable and then switch to the next release once that's out.
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#6001
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?