Skip to content

Conversation

@wielinde
Copy link
Member

@wielinde wielinde commented Dec 27, 2025

Ticket

https://community.openproject.org/work_packages/70191

What are you trying to accomplish?

I want to allow the same search and filter (type, status, meta status, project name) capabilities when picking a work package

  • to book time on
  • to add to board
  • to create relations, parent or child
  • to filter on work package IDs
    • Don't filter on loaded data but always use the backend's full capabilities (Oliver Günther Specially about this part I would love to know your opinion)
  • to add to meeting agenda
  • to filter cost reports

We already have this in the global search and when hash mentioning a work package. Users get used to it and miss it in the other places.

What approach did you choose and why?

This PR replaces the subjectOrId filters by typeahead filters which comes with more user friendly capabilities.

When filtering work packages by ID, the filter's frontend component allowed to search by subject or ID. And when the data set was already loaded to the frontend, it did search directly on the loaded data, as it does for other attributes. As I want the user to have all the typeahead features also in that situation, I added an exception so that it now will still use the backend for the typeahead logic. I am not sure if that has stronger performance implications as I don't know why that exactly it was built like this in the first place.

Merge checklist

  • Added/updated tests
  • Added/updated documentation in Lookbook (patterns, previews, etc)
  • Tested major browsers (Chrome, Firefox, Edge, ...)

@github-actions github-actions bot temporarily deployed to gh-6899875-pr-21522 December 27, 2025 12:25 Inactive
@github-actions github-actions bot temporarily deployed to gh-6899875-pr-21522 December 29, 2025 21:39 Inactive
@github-actions github-actions bot temporarily deployed to gh-6899875-pr-21522 December 29, 2025 22:14 Inactive
…all results were loaded so that all typeahead capabilities are used.
@wielinde wielinde marked this pull request as ready for review December 31, 2025 08:15
@github-actions
Copy link

Caution

The provided work package version does not match the core version

Details:

Please make sure that:

  • The work package version OR your pull request target branch is correct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants