Releases API

Numeric ID or key of the product

Name of the release

Email or ID of the user that will own this release

Array of names or ids of initiatives which this release is associated with.

Status of the release — must be a valid status for the selected product.

Numeric ID of the roll-up release of the release if present

Theme of the release — may include HTML formatting.

Start date of the release in format YYYY-MM-DD

End date of the release in format YYYY-MM-DD

Release date of the release in format YYYY-MM-DD

Date development started in format YYYY-MM-DD

Sets whether this release is a parking lot. Use true to represent a parking lot release

The external release date for this release in format YYYY-MM-DD

Rounds the external release date to the nearest resolution value. This must be specified along with an external release date and must be one of: sync, exact, week, month, quarter, half, year

The units for this release — must be either "time" or "story_points".

The total capacity in time or story points for this release, depending on the capacity units configured.

For time: use min, h, d, w, m. Example: "2d 1h”.

1d = 8h, 1w = 5d, 1m = 22d.

For story points: Use p to represent points. Example: "4p”.

Source for calculating progress on the release. Options are: progress_manual, progress_from_features, progress_from_release_phases, progress_from_todos, progress_from_remaining_estimate, progress_from_features_completed, progress_from_epics.

Progress completed on the release — may only be set when the progress_source is manual.

Source for automatically calculating start and end dates. Options are: duration_manual, duration_from_release_phases_features, duration_from_sub_releases.