Epic Tools

Four tools for managing epics: create, update, get (with progress data), and delete.

Permission Model

• Getting epics: any project member
• Creating epics: Team Lead+ role required
• Updating epics: Team Lead+ role required
• Deleting epics: Manager+ role required

Enums

Colors

Value	Color
0	Grey
1	Green
2	Blue
3	Red
4	Purple
5	Yellow

Status

Value	Status
0	Open
1	In Progress
2	Completed

create-epic

Create a new epic to group and order issues on the timeline.

Parameters

Parameter	Type	Required	Description
project_id	integer	Yes	The project to create the epic in
title	string	Yes	Epic title (max 255 characters)
color	integer	Yes	Color code (0–5, see table above)
description	string	No	Epic description
start	date	No	Start date (ISO 8601). Required if end is provided.
end	date	No	End date (ISO 8601). Must be after start. Required if start is provided.
order	integer	No	Display order (default 0, minimum 0)
issue_ids	array	No	Issue IDs to attach (must belong to the same project)

Behavior

• Created with Open status by default
• Start and end dates must be provided together — you can't set one without the other
• All issue IDs are validated to belong to the specified project
• Requires Team Lead+ role

Example Prompt

Create a red epic called "Q1 Auth Overhaul" in the kendo project for the month of April. Attach the three auth-related issues we created earlier.

update-epic

Update an existing epic's details, status, dates, or issue assignments.

Parameters

Parameter	Type	Required	Description
epic_id	integer	Yes	The epic to update
title	string	No	New title (max 255 characters)
description	string	No	New description, or null to clear
status	integer	No	0 Open, 1 In Progress, 2 Completed
color	integer	No	Color code (0–5)
start	date	No	New start date. Required if end is provided.
end	date	No	New end date. Must be after start.
order	integer	No	New display order (minimum 0)
issue_ids	array	No	Complete list of issue IDs to attach. Omit to keep current assignments. Pass [] to detach all.

Behavior

• Only provided fields are updated
• Omitting issue_ids preserves current issue assignments; passing [] detaches all issues
• Requires Team Lead+ role

Example Prompt

Mark the "Auth Overhaul" epic as in progress and push the deadline to mid-May

get-epics

Get epics for a project with full issue details and progress data. Read-only and safe to call repeatedly.

Parameters

Parameter	Type	Required	Description
project_id	integer	Yes	The project to get epics for
epic_id	integer	No	Get a single epic by ID
status	integer	No	Filter by status (0 Open, 1 In Progress, 2 Completed)

Behavior

• Returns epics with full issue details (key, title, lane, assignee)
• Includes progress data: completed issues (those in the project's last lane) vs total
• Results ordered by display order
• Marked as #[IsReadOnly] and #[IsIdempotent]

Example Prompt

What epics are currently in progress in the kendo project? Show me their progress.

delete-epic

Permanently delete an epic.

Destructive

This action cannot be undone. The epic is permanently removed. Issues linked to the epic are NOT deleted — only the epic association is removed.

Parameters

Parameter	Type	Required	Description
epic_id	integer	Yes	The epic to delete

Behavior

• Issues linked to the epic are preserved — only the epic grouping is removed
• Requires Manager+ role (higher than create/update)

Example Prompt

Delete the "Auth Overhaul" epic, we're restructuring the roadmap

See Also

• Resources — Read epic data via kendo://projects/{id}/epics
• Projects Guide — Understanding epics and timeline planning
• Epics API — REST endpoints for epic management