Juscribe

Create a new ticket in the workspace. Returns the created ticket, with notes when it matches another ticket. A new ticket goes to the bottom of the Backlog. When the person asks for the Icebox, it goes to the top of the Icebox. Place one anywhere else only when the person asks. In the description, Open with a sentence or two in plain words saying what happened or what is asked, before any detail. Write #123 only for a ticket number, and p45 for a project.

create_ticket

Create a workspace, a new board of its own. Use it only when the person asks for a new board. Juscribe allows it when the person this agent acts for is an owner of the organization and its plan has room for another; otherwise it refuses and nothing is made. Answers with the id the other tools take as workspace_id.

create_workspace

File a list of tasks in one call, such as the action items from meeting notes. Every item is checked as create_ticket checks one, and one bad item stops the whole batch before anything is written. Items go to the bottom of the Backlog in the order given; an item whose panel is icebox goes to the top of the Icebox, which the person has to ask for. Place one elsewhere afterwards with move_ticket. The reply says what happened to each item.

create_tickets

Delete a comment from a ticket for good. Only a comment you wrote can be deleted; anyone else's is refused. The comment id is in get_ticket.

delete_comment

Take a step off a ticket's checklist for good. To mark one done instead, use update_subtask with completed: true.

delete_subtask

Replace the text of a comment on a ticket. Only a comment you wrote can be changed; anyone else's is refused. The comment id is in get_ticket.

update_comment

One project in full: its description, where its plan lives, who asked for it and who owns it, and the counts of its tickets. Its tickets are list_tickets with project_id.

get_project

Get full details for a single ticket, including comments and attachments.

get_ticket

The iteration in progress: its number, dates, committed and accepted points, and its tickets, 50 to a page. Use this rather than list_iterations, which returns every iteration the board has had.

get_current_iteration

List what blocks a ticket, or with direction "blocks", what it blocks. Resolved blockers are included with resolved_at set. The ids here are what resolve_blocker takes.

list_blockers

List a ticket's subtasks: its ordered steps, each with at most one owner. The ids here are what the other subtask tools take.

list_subtasks

List iterations (sprints) for a workspace, with velocity and point data.

list_iterations

List the labels on the board, with the ids that label_ids takes.

list_labels

List the people and agents on the board, with the user ids that assignee_ids and stakeholder_id take. Mention someone by @username: names are not unique.

list_people

List all projects in a workspace with their state and position.

list_projects

List tickets in a workspace with optional filters — panel, state, type, project, assignee, label, iteration, what changed since a moment, when they were created, when they are due, or a search — 50 to a page, in board order or by due date. A panel comes with its release, milestone and deadline markers. The reply says when more pages exist, and when markers were left out.

list_tickets

List the workspaces this connection can reach, with the ids the other tools take as workspace_id.

list_workspaces

Move a subtask to a place in its ticket's list, counting from 1. A place past the end moves it to the bottom.

move_subtask

Put a ticket directly above (before) or below (after) another ticket in the same panel. This is how the backlog is prioritised. Moving between panels is update_ticket or transition_ticket.

move_ticket

Read a file attached to a ticket, from get_ticket's attachments: a photo comes back as an image, a PDF or a text, CSV, Markdown or JSON file as text. A long file is cut at 150,000 characters and says so; an archive or other kind is refused by name, with the ticket's link so the person can open it in the app.

get_attachment

Mark a blocker resolved, which unblocks the ticket once none is left. Get its id from list_blockers.

resolve_blocker

Search tickets, projects, comments and people at once. Matches label and project names too, and ranks an exact ticket or project number first. Results are compact: use get_ticket for detail.

search

Send delivered work back to be redone, on the person's explicit request in this conversation and after confirming with them. The reason is required and is posted on the ticket as a comment, so it says why it came back.

reject_ticket

Change a project's name, description, colour or stakeholder. Only the fields passed change. Moving, sealing or deleting a project is done in the app.

update_project

Change a subtask. Set completed to the value you want: true ticks it and false reopens it, and calling either twice changes nothing. Only the fields passed change.

update_subtask

Update an existing ticket's fields. Only provided fields are changed. Before changing a description, read the ticket with get_ticket first. Text a person wrote stays word for word, with anything you add below a --- line, and you edit your own earlier additions in place, so they are not stacked as dated updates. To only add below the text, use append_to_description.

update_ticket

Get a condensed overview of the workspace board: panel counts, projects, velocity, users, and ticket summaries for the current and backlog panels unless others are named. Release, milestone and deadline markers are included, and counted. Use this to orient yourself before drilling into specific tickets.

get_workspace_summary