github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2346] ParadeDB search results are too strict / insufficient in Vikunja 2.x #6646

New Issue
Closed
opened 2026-04-20 17:14:25 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:14:25 -05:00
Owner
Copy Link

Originally created by @wucherpfennig on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2346

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

Hello

I’m running Vikunja 2.x with ParadeDB enabled as documented. In practice, however, the search results are much more restrictive than expected.

Observed behavior:

  • Results are only returned when entering the exact full word.
  • Close variants are not found (e.g. singular vs. plural or small typos).
  • Word prefixes or partial terms do not return results (e.g. searching for landing does not find landingpages).

Example:

  1. Create a task with the title: “Landingpages update”.

  2. Search for:

    • landing → no results
    • landingpage → no results
    • landingpages → result found

Expected behavior:

  • “Fuzzy matching” should tolerate small variations (e.g. missing or additional character).
  • Searching by a common word prefix should return relevant matches when the term clearly exists in the title or description.
  • Overall, search should be more forgiving and practical for real-world usage.

Currently, the behavior feels closer to strict token matching than to fuzzy full-text search.

Could you please clarify whether this is intended behavior of the current ParadeDB integration, or if this is a regression or configuration issue?

Thank you

Vikunja Version

2.1.0

Browser and version

Firefox / Chrome

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @wucherpfennig on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2346 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Hello I’m running Vikunja 2.x with ParadeDB enabled as documented. In practice, however, the search results are much more restrictive than expected. Observed behavior: * Results are only returned when entering the exact full word. * Close variants are not found (e.g. singular vs. plural or small typos). * Word prefixes or partial terms do not return results (e.g. searching for `landing` does not find `landingpages`). Example: 1. Create a task with the title: “Landingpages update”. 2. Search for: * `landing` → no results * `landingpage` → no results * `landingpages` → result found Expected behavior: * “Fuzzy matching” should tolerate small variations (e.g. missing or additional character). * Searching by a common word prefix should return relevant matches when the term clearly exists in the title or description. * Overall, search should be more forgiving and practical for real-world usage. Currently, the behavior feels closer to strict token matching than to fuzzy full-text search. Could you please clarify whether this is intended behavior of the current ParadeDB integration, or if this is a regression or configuration issue? Thank you ### Vikunja Version 2.1.0 ### Browser and version Firefox / Chrome ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:14:27 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Mar 5, 2026):

This issue has been fixed in #2364, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

<!-- gh-comment-id:4004880665 --> @vikunja-bot-app[bot] commented on GitHub (Mar 5, 2026): This issue has been fixed in #2364, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
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#6646
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?