Actions57
- Label Actions
- Project Actions
- Add a Team
- Add a User
- Create
- Create a Kanban Bucket
- Create a Link Share
- Create a Project View
- Delete
- Delete a Kanban Bucket
- Delete a Link Share
- Delete a Project View
- Duplicate
- Get
- Get All Link Shares
- Get All Project Views
- Get All Teams
- Get All Users
- Remove a Team From a Project
- Remove a User From a Project
- Update
- Update a Kanban Bucket
- Update a Project View
- Update a Team's Rights on a Project
- Update a User's Rights on a Project
- Task Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to create a new Project View within a specified project. A Project View in Vikunja is a customizable way to visualize tasks and buckets, such as in list, Gantt chart, table, or Kanban board formats. This operation is useful for users who want to organize and display their project tasks in different layouts tailored to their workflow preferences.
Common scenarios include:
- Creating a new Kanban board view for a project to manage tasks visually.
- Setting up a Gantt chart view to track task timelines.
- Defining default and done buckets to automate task status management.
- Applying filters to focus on specific subsets of tasks within a project.
Practical example: A project manager wants to add a "Sprint Backlog" Kanban view to a software development project, specifying which bucket new tasks should default to and which bucket marks tasks as done.
Properties
Name | Meaning |
---|---|
Project Title or ID | The target project where the new view will be created. You can select from a searchable list of projects or specify the project by its ID. |
Project View Title | The title/name of the new project view you want to create. |
View Kind | The type of view to create. Options are: List, Gantt, Table, Kanban. Determines how tasks and buckets are displayed. |
Bucket Configuration Mode | How buckets are configured in this view. Options: None (no buckets), Manual (buckets managed manually), Filter (buckets filtered automatically). |
Default Bucket ID | (Optional) The ID of the bucket where new tasks without an assigned bucket will be added. Defaults to the leftmost bucket if not set. |
Done Bucket ID | (Optional) The ID of the bucket that marks tasks as done when tasks are moved into it. Tasks marked done individually are also moved here. |
Project View Filter | (Optional) A filter expression to limit which tasks are shown in this view. |
Output
The node outputs JSON data representing the newly created Project View object as returned by the Vikunja API. This typically includes details such as the view's ID, title, kind, bucket configuration, and any other metadata related to the view.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL of the Vikunja instance must be configured in the node credentials.
- Network access to the Vikunja server is necessary.
Troubleshooting
- Invalid Project ID or Project Not Found: Ensure the project ID or selected project exists and is accessible with the provided API credentials.
- Missing Required Fields: The "Project View Title", "View Kind", and "Bucket Configuration Mode" are required. Omitting these will cause errors.
- API Authentication Errors: Verify that the API key credential is valid and has sufficient permissions to create project views.
- Incorrect Bucket IDs: If specifying default or done bucket IDs, ensure they exist within the project; otherwise, the API may reject the request.
- Filter Syntax Issues: If using a filter expression, confirm it follows the expected syntax supported by Vikunja to avoid filtering errors.