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 task management API to add a relation between two tasks. It allows users to define how one task is related to another, such as marking one task as blocking another, setting parent-child relationships, or indicating duplicates.
Common scenarios include:
- Linking dependent tasks where one task blocks another.
- Organizing subtasks under a main task.
- Marking tasks as duplicates or copies of each other.
- Establishing task sequences like "follows" or "precedes".
Practical example: In a project management workflow, you might use this node to mark that Task A is blocked by Task B, so Task A cannot proceed until Task B is completed.
Properties
| Name | Meaning |
|---|---|
| Task ID | The ID of the primary task to which you want to add a relation. |
| Other Task ID | The ID of the other task you want to relate the current one with. |
| Relation Kind | The kind of relation between tasks. Options: 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 adding the relation between tasks. This typically includes confirmation details about the created relation, such as IDs and relation type.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- The node sends HTTP requests to the Vikunja API endpoints to manage task relations.
Troubleshooting
- Invalid Task IDs: If either Task ID or Other Task ID does not exist, the API will return an error. Verify that both task IDs are correct and accessible.
- Permission Errors: Ensure the API key has sufficient permissions to modify tasks and their relations.
- Relation Kind Errors: Using an unsupported relation kind value may cause errors. Use only the provided options.
- API Connectivity Issues: Check network connectivity and the correctness of the Vikunja API URL in credentials.
Links and References
- Vikunja API Documentation
- Task Relations Concept in Vikunja (general reference)