Actions60
- 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
- Get Many
- 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 Permissions on a Project
- Update a User's Permissions on a Project
- Task Actions
- Team Actions
- Webhook Actions
Task → Remove an Assigned User From a Task
AI-generatedOverview
This node operation removes an assigned user from a specific task in Vikunja. It is useful in scenarios where task assignments need to be updated, such as when a user is no longer responsible for a task or when reassigning tasks among team members. For example, a project manager can use this operation to unassign a user from a task that has been completed or reassigned.
Use Case Examples
- Unassign a user from a task when they are no longer responsible for it.
- Remove a user assignment to update task ownership in a project management workflow.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task from which the user will be removed. This is a required field to specify the target task. |
| User ID | The unique identifier of the user to be removed from the task. This is required to specify which user assignment to remove. |
| Request Options | Additional settings for the request such as batching, SSL certificate validation, proxy configuration, and timeout settings. These options allow customization of the API request behavior. |
Output
JSON
success- Indicates whether the user was successfully removed from the task.taskId- The ID of the task from which the user was unassigned.userId- The ID of the user who was removed from the task.
Dependencies
- An API key credential for Vikunja API authentication
Troubleshooting
- Ensure that the Task ID and User ID are valid and correspond to existing entities in Vikunja.
- Check API credentials and permissions to confirm the node has rights to modify task assignments.
- If SSL issues occur, consider enabling the 'Ignore SSL Issues' option if appropriate.
- Verify proxy settings if a proxy is used to connect to the Vikunja API.