This could be a feature request, but it’s more broadly an ask if there’s a way I can implement this use-case in Vikunja.
I am working on setting up Vikunja for a collectively run community space that has a large membership with disparate levels of engagement and buy-in.
We have several committees set up dedicated to particular domains of running the space, but we’d also like to make it easier for the broader community to engage in this work with us. I am assuming that each committee (facilities, finance, tech etc) will have at least its own project, maybe multiple.
I had an idea for an “Open Call” label that would be applied to any task that would be appropriate for someone to take on without requiring an onboarding process (sort of like a “good first bug” label in a bugtracker). We would then link to a filtered list of all the Open Call tasks from our homepage, and it would become a low-barrier-to-entry way to plug into the space.
It doesn’t seem like it’s possible to share a public view of filters, but is there some other way to accomplish what I’m describing? I am still pretty new to Vikunja.
Currently, it’s not possible to share a saved filter publicly via link share, but you could create a view that is based on a filter and then use a link share to share that publicly.
In your case, it might make more sense to write some code to have your website talk to the Vikunia API directly and display the tasks of a saved filter (via an authenticated user) that way instead of going through a link share.
I’m attempting to do that via the API now. I make an api token with all permissions and am attempting to filter tasks by labels but am getting the following error. I am able to filter by assignee successfully but i get the same error below for existing and non-existent labels. Am I doing something wrong? This is on vikunja 0.24.6
2025-12-10T21:42:03.320887472Z 2025-12-10T21:42:03Z: ERROR ▶ d7d Task filter value is invalid [Value: opencall, Field: labels]
2025-12-10T21:42:03.321480988Z 2025-12-10T21:42:03Z: WEB ▶ 10.0.0.2 GET 400 /api/v1/tasks/all?filter=labels%20in%20’opencall’ 20.643766ms - python-requests/2.32.5
2025-12-10T21:42:09.950868182Z 2025-12-10T21:42:09Z: ERROR ▶ d86 Task filter value is invalid [Value: opencall, Field: labels]
2025-12-10T21:42:09.950877806Z 2025-12-10T21:42:09Z: WEB ▶ 10.0.0.2 GET 400 /api/v1/tasks/all?filter=labels%20in%20opencall 24.310883ms - python-requests/2.32.5
2025-12-10T21:42:15.959533314Z 2025-12-10T21:42:15Z: ERROR ▶ d8d Task filter value is invalid [Value: opencall, Field: labels]
2025-12-10T21:42:15.960132281Z 2025-12-10T21:42:15Z: WEB ▶ 10.0.0.2 GET 400 /api/v1/tasks/all?filter=labels%20=%20opencall 34.500138ms - python-requests/2.32.5
or @kolaente, what specifically do you mean by “create a view that is based on a filter”– do you mean “view” in a way that is specific to Vikunja or is the view here the result of using the API?
