Link Ticketing Project
Have a launch follow its work in a ticketing system, by its address,
replacing anything it followed, as pasting it on the launch’s page
does: a Linear project, a Jira epic or issue, a GitHub organization’s
project or a repository’s milestone, an Asana project, or a ClickUp
list or task. One in a system connected to the workspace must be one
the connection can see (in its Linear workspace, on one of its Jira
sites, in the GitHub organization the app is installed on, or in its
Asana or ClickUp workspaces), and syncs at once: the answer’s
ticketingProject says how that went. Any other address, a whole
Jira project, a GitHub repository, or a ClickUp folder or space
included, is kept as a link and does not sync. It reads the system,
so it shares the ticketing-sync budget with a sync. 404 not_found
when the connection cannot find or see the project, 409 conflict
for one in another workspace or site of the system than the one
connected, 409 ticketing_reconnect when the system turned the
connection down (a workspace admin connects it again in Settings →
Integrations), and 502 upstream_error when it did not answer.
Needs launches:write.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Request
Its address, as copied from the browser: a Linear project
(https://linear.app/acme/project/checkout-v2-1a2b3c), a Jira epic
or issue (https://acme.atlassian.net/browse/CHK-12, or a board
with it open), a GitHub organization’s project
(https://github.com/orgs/acme/projects/12) or a repository’s
milestone (https://github.com/acme/web/milestone/3), an Asana
project (https://app.asana.com/1/<workspace>/project/<project>),
or a ClickUp list (https://app.clickup.com/<workspace>/v/li/<list>)
or task (https://app.clickup.com/t/<task>). Anything else, a
ClickUp folder or space included, is kept as a link.
Response
Held back until published: nobody has been told about it, its steps
are in no review queue, and it cannot be launched. A draft is never
LAUNCHED: launching it, adding one as a draft with that status, or
setting status to LAUNCHED on it is a 409 draft, unless the
same request publishes it with draft: false.
Share of steps that have been approved, excepted or marked N/A.
The first of owners, from when a launch had one. Read owners.
The first owner’s id. Read owners.
The first of teams, from when a launch had one. Read teams.
As its newest update says; null until somebody posts one, and once the launch has launched. See /launches/{launchId}/posts.
The launch template its steps come from. See /launch-templates.
The ticketing project it follows, if somebody linked one. See /launches/{launchId}/ticketing-project.