Dillie

Collects a task and its subtasks recursively and returns them as a tree (each node has id, issueKey, title, status, issueType, children). status and issueType are replaced with option labels. depth counts the root (1 means the root only; the default is the whole tree).

dillie_get_task_tree

Gets a project's details (name, description, status, owner, etc.) by project ID.

dillie_get_project

Gets the IDs of a project's sub-resources (the task list's listId, root folder, overview canvas, channel, etc.). Call this first to get a listId before using task tools such as dillie_query_tasks. The IDs in the response are identifiers meant only as arguments to subsequent tool calls.

dillie_get_project_resources

Gets task statistics for **one** project (total counts and counts by status and by type, completion rate, progress per top-level task). This is not a cross-project summary — to cover several projects, iterate with dillie_list_projects and call it for each. The by-status and by-type keys are option IDs; get their labels from dillie_list_fields.

dillie_get_project_stats

Gets the field definitions of a task list (name, type, role, options, etc.). Use it to find the IDs of role-based fields such as assignee (ASSIGNEE) and status (STATUS), or the fieldIds to put in values when creating or updating a task.

dillie_list_fields

Lists a project's members, including user details. Use it to check that a user exists before specifying an assignee by name.

dillie_list_members

Lists dillie projects, optionally filtered by status or a name search term. Use it to find a project ID before working with a specific project. The id in the response is the identifier passed as the projectId argument of other tools.

dillie_list_projects

Lists the public docs for a locale (and optionally a nav section) as a flat list (product, slug, title, section, navOrder). For the hierarchy use dillie_platform_docs_nav; for full text use dillie_read_platform_doc. No sign-in required.

dillie_list_platform_docs

Lists the sprints of a list (agile mode), in all states (FUTURE/ACTIVE/COMPLETED). The id in the response is the sprintId argument of the sprint tools.

dillie_list_sprints

Gets the nav tree of the public docs (hierarchy of sections and documents). Use each document's product and slug to read its full text with dillie_read_platform_doc. No sign-in required.

dillie_platform_docs_nav

Queries a project's tasks (list items) with filters, sorting and cursor pagination. If assignee is a member name, it is turned into a userId filter automatically in two steps: look up the member list, then look up the ASSIGNEE field ID. With topLevelOnly, only top-level (root) tasks are returned. The id of each item in the response is the itemId argument of follow-up tools such as dillie_get_task. For the signed-in user's own tasks, pass assignee "me".

dillie_query_tasks

Gets the full body (MDX) and frontmatter of a single public document by product and slug. Use it when search excerpts alone are not enough and the answer must rest on the full document. Get product and slug from the nav tree. No sign-in required.

dillie_read_platform_doc

Runs a hybrid search over the public Dillie platform docs (product guides and docs). When answering questions about platform features, usage or policies, base the answer on the excerpts and cite the url as the source. No sign-in required.

dillie_search_platform_docs

**Overwrites the entire** task description with Markdown (it does not append — the previous body is lost and cannot be restored). To add to it, merge your text into the original from dillie_get_task_description and pass the result. The server rejects HTML tags with 400.

dillie_set_task_description

Transitions a FUTURE sprint to ACTIVE. There is no tool to undo this. A list can have several ACTIVE sprints — starting is not rejected while another sprint is in progress, so if only one should run, check with dillie_list_sprints first. The server rejects sprints that are not FUTURE.

dillie_start_sprint

Updates an existing task's (list item's) field values, parent item (parentItemId) and color. values only needs the fieldId → value pairs to change. The previous values of the fields you pass are overwritten and cannot be restored. Completing or cancelling is done with dillie_complete_task or dillie_cancel_task, not this tool (the server rejects setting done directly).

dillie_update_task