feat: start a project from another one's configuration
Creating a project can name one the creator owns or administers: its statuses, transitions, types, areas, custom fields and automation rules are copied once (paused rules stay paused; rules assigning to someone who is not in the new project are left out). GraphQL templateProjectId, REST template (id or key), MCP create_project template, and a select in the web's new-project form. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -116,6 +116,8 @@ export type CreateProjectInput = {
|
||||
/** 2-10 chars, e.g. "TS" → tickets TS-1, TS-2... */
|
||||
key: string;
|
||||
name: string;
|
||||
/** A project you own or administer to start from: its statuses, transitions, types, areas, custom fields and automation rules are copied */
|
||||
templateProjectId?: string | null | undefined;
|
||||
};
|
||||
|
||||
export type CreateReleaseInput = {
|
||||
|
||||
Reference in New Issue
Block a user