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
- Team Actions
- Task Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to manage task relations within a project management context. Specifically, the "Remove a Relation" operation under the "Task" resource allows users to delete an existing relationship between two tasks. This is useful in scenarios where task dependencies or associations change over time, such as removing a "blocked by" or "duplicate of" link between tasks.
Practical examples include:
- Removing a "blocked" relation when a blocking issue is resolved.
- Detaching subtasks from a parent task if they are no longer relevant.
- Clearing duplicate task links after merging or consolidating tasks.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the primary task from which the relation will be removed. |
| Other Task ID | The unique identifier of the other task involved in the relation to be removed. |
| Relation Kind | The type of relation between the two tasks. Options include: Blocked, Blocking, Copied To, Copied From, Duplicate Of, Duplicates, Follows, Parent Task, Precedes, Related Task, Sub Task. |
Output
The node outputs JSON data representing the result of the remove relation operation. Typically, this would confirm whether the relation was successfully deleted or provide details about the updated task state. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- The node sends HTTP requests to the Vikunja REST API endpoints related to tasks and their relations.
Troubleshooting
Common Issues:
- Invalid or missing Task ID or Other Task ID can cause the API call to fail.
- Incorrect Relation Kind value may lead to errors or no action taken.
- Network connectivity issues or incorrect API URL configuration can prevent successful communication with the Vikunja server.
- Insufficient permissions on the API key might block modification of task relations.
Error Messages:
- "404 Not Found" — The specified task(s) do not exist; verify Task IDs.
- "401 Unauthorized" — Authentication failed; check API key validity.
- "400 Bad Request" — Likely due to invalid parameters such as unsupported relation kind.
Resolutions:
- Double-check all input IDs and relation kind values.
- Ensure the API key has appropriate permissions.
- Verify the API URL and network access.
- Consult Vikunja API documentation for valid relation kinds and request formats.