OpenProject icon

OpenProject

Interact with OpenProject via API
Join our community

Actions199

Overview

This node operation allows you to create a new work package within a specified project in OpenProject. Work packages are units of work or tasks that can be tracked and managed within projects. This operation is useful for automating task creation workflows, integrating project management with other systems, or bulk-creating tasks based on external triggers.

Practical examples include:

  • Automatically creating development tasks when a new feature request is logged.
  • Generating bug fix work packages from an issue tracking system.
  • Scheduling and assigning tasks dynamically based on incoming data.

Properties

Name Meaning
Id ID of the project where the work package will be created (required).
Subject The title or subject of the work package.
Description Detailed description of the work package, supporting markdown format.
Schedule Manually Boolean flag indicating if scheduling should be manual (true) or automatic (false).
Start Date Scheduled start date of the work package.
Due Date Scheduled end date of the work package.
Estimated Time Estimated time required to complete the work package, excluding any subtasks or descendants.
Duration Duration in hours needed to complete the work package. Must be at least one day (P1D), rounded down to nearest day. Has no effect unless start or due date is set. Not applicable for milestone type work packages.
Ignore Non Working Days Boolean flag indicating whether non-working days should be ignored during scheduling. If true, the work package can be scheduled on non-working days.
Links JSON object containing references to related entities such as category, type, priority, project, status, responsible person, assignee, version, and parent work package. These define relationships and metadata for the work package.

Output

The node outputs JSON data representing the newly created work package as returned by the OpenProject API. This includes all details of the work package such as its ID, subject, description, scheduling information, links to related entities, and status.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the OpenProject API.
  • The base URL of the OpenProject instance must be configured in the node credentials.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Missing or invalid project ID: Ensure the project ID provided exists and is accessible with your API credentials.
  • Invalid date formats: Start Date and Due Date must be valid date strings recognizable by the API.
  • Duration constraints: Duration must be at least one day and will be floored to the nearest day; setting it incorrectly may cause errors.
  • Permission errors: Make sure the API key has sufficient permissions to create work packages in the target project.
  • Malformed JSON in Description or Links: The description and links fields expect valid JSON; malformed input will cause request failures.
  • Scheduling conflicts: If scheduling automatically, conflicts with non-working days or dependencies might cause unexpected results; use the "Ignore Non Working Days" flag accordingly.

Links and References

Discussion