No filters working (assignee, date, task done, etc.)

Bug
1

Hi! I’m hosting Vikunja 0.22 with authentik oidc and docker compose.
I’m seeing the following issues:

  • When I mark tasks as done, they won’t disappear from the list view. Regardless of the filter settings.
  • When I move a task to a subproject, it won’t show in the subproject, but remain within the main project. Although it’s correctly showing that it belongs to the subproject.
  • When I add a task in gantt view it’s correctly displayed with start and end date, but when I add a start and end date to a task that was created in list view, it does not show up in gantt view

Now, all of these problems don’t reproduce in the version on try.vikunja. So what I did was upgrading my docker compose to the unstable tag, same version as try.vikunja. However, the before mentioned issues were still there.
Could this be a bug related to using

  • sqlite
  • typesense

Thanks for your time!

This is my docker-compose.yml

version: '3'

services:
  api:
    image: vikunja/api
    environment:
      VIKUNJA_SERVICE_JWTSECRET: ***
      VIKUNJA_SERVICE_FRONTENDURL: ***
      VIKUNJA_DATABASE_PATH: /db/vikunja.db
      VIKUNJA_TYPESENSE_ENABLED: true
      VIKUNJA_TYPESENSE_URL: "http://typesense:8108"
      VIKUNJA_TYPESENSE_APIKEY: ${API_KEY}

    volumes:
      - ./files:/app/vikunja/files
      - ./db:/db
      - ./config.yml:/app/vikunja/config.yml
    networks:
      - web
      - default
    restart: unless-stopped
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.vikunja-api.rule=Host(`***`) && (PathPrefix(`/api/v1`) || PathPrefix(`/dav/`) || PathPrefix(`/.well-known/`))"
      - "traefik.http.routers.vikunja-api.entrypoints=websecure"
      - "traefik.http.routers.vikunja-api.tls.certResolver=myresolver"
  frontend:
    image: vikunja/frontend
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.vikunja-frontend.rule=Host(`***`)"
      - "traefik.http.routers.vikunja-frontend.entrypoints=websecure"
      - "traefik.http.routers.vikunja-frontend.tls.certResolver=myresolver"
    networks:
      - web
      - default
    restart: unless-stopped
  typesense:
    image: typesense/typesense:0.25.2
    restart: on-failure
    volumes:
      - ./typesense-data:/data
    command: '--data-dir /data --api-key=${API_KEY} --enable-cors'

networks:
  web:
    external: true
~
2

I’ve noticed similar things. My guess is this I’d related to typesense. Do you see the same problems without the typesense integration?

3

Aha! setting VIKUNJA_TYPESENSE_ENABLED: false resolved all issues mentioned.
Thank you!

4

I’d say that’s more a temporary workaround than a solution - I’ll look into a fix.

5

This should now be fixed in 90ad975ca0. Please check with the next unstable build.