Migration from Vikunja export duplicated boards [Local to OIDC]

Support
1

I recently upgraded my security on my instance of Vikunja, and decided to just do an export of my local account data, then import it to the newly created OIDC. I have already been through (most) of the threads regarding migration, like this one:

I dont know too much about database manipulation, so thought just simply migrating the tasks would do the trick. However, post import it seems I have two of each board on the imported projects:

Imported projects

image
image642×129 6.46 KB

I double checked by creating a new project in my OIDC account, and dont have the issue with newly created projects, just imported ones:

Created project boards

image

Im sure I could figure out the db manipulation, i just migrated a mysql db user using DBeaver, just thought I might reach out to see if there were a simple solution I was missing

2

This looks like a bug. Will take a look.

3

I have the same problem, and some of my tasks are appearing duplicated in more than one bucket

4

This is now fixed in 28b4eaee31, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

5

Can confirm this worked, @bruno, I had to delete and reimport my old export, so if you created any new projects that you want migrated, back that up as well, I had just a few tasks so I am just rebuilding them.

6

Could you help me with how to do this update? I use Vikunja on a Docker, how do I update it to the unstable build? Regarding the backup, just do that export again from within the database, correct? the same is in the documentation

7

in your compose change the following:

services:
    vikunja:
        image: vikunja/vikunja

to:

services:
    vikunja:
        image: vikunja/vikunja:unstable

@kolaente, if you have a better answer to :

my solution was just exporting from the frontend and reimporting on recreate. Not too handy with database manipulation yet.

8

Thanks for the feedback, I did the following step-by-step:

  1. extract the application database, as instructed in the documentation.
  2. I stopped vikunja docker, changed it to unstable as you indicated
  3. I did docker compose up -d --force-recreate
  4. I entered the DB docker, and imported the DB that I had exported before.

Despite everything, it’s still the same thing, it’s still duplicated, I don’t know if I did something wrong.

In this print you can see that card #63 is appearing duplicated, both in Inbox and in Someday/Maybe:
Screenshot from 2024-08-12 14-32-18

9

This seems to be a similar but unrelated bug, I would create a new post for better tracking in the future, my issue was with dupicalte boards, as in two Gannt - Table - List boards etc. Your issue looks to be task duplication No longer able to properly move tasks between Kanban columns or Task - duplicated

10

There’s one small issue I believe - when Vikunja starts, it performs database migrations to migrate the database schema (if needed) to the current version. In your steps, you’ve imported data after Vikunja started, so the database migrations where completed and then you inserted an old database again.

You should make a copy of the database as a backup, then simply update to unstable (your steps 2 and 3, although --force-recreate isn’t neccessary) and skip step 4, as Vikunja would automatically update the database in place.

1 Like