Actions15
- Work Package Actions
- Project Actions
- Time Entry Actions
- Custom API Call Actions
Overview
This node operation retrieves a specific work package from the OpenProject system by its ID. It is useful in scenarios where detailed information about a particular work package is needed, such as project management, tracking tasks, or integrating work package data into other workflows. For example, a user can fetch the status, priority, assignee, and other details of a work package to monitor progress or update related systems.
Use Case Examples
- Fetching a work package by its ID to display its details in a dashboard.
- Retrieving a work package to check its current status before updating it.
- Integrating with other tools to synchronize work package information.
Properties
| Name | Meaning |
|---|---|
| Work Package ID | The unique identifier of the work package to retrieve. This is a required string input. |
Output
JSON
jsonid- The unique identifier of the retrieved work package.subject- The subject or title of the work package.description
*raw- The raw description text of the work package.status- The current status of the work package.priority- The priority level of the work package.assignee- Information about the user assigned to the work package.startDate- The start date of the work package.dueDate- The due date of the work package.estimatedTime- The estimated time to complete the work package, typically in ISO 8601 duration format.
Dependencies
- OpenProject API with API token authentication
Troubleshooting
- Ensure the Work Package ID is valid and exists in the OpenProject system to avoid 'not found' errors.
- Check that the API token credential is correctly configured and has sufficient permissions to access work package data.
- If the node returns an error about invalid JSON, verify that all input parameters are correctly formatted and no unexpected characters are present.
Links
- OpenProject API Documentation - Official documentation for the OpenProject API, including endpoints for work packages.