Juscribe

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.

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.

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

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.

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.

Save something you wrote — a newsletter draft, a volunteer list, meeting notes — onto a ticket as a Markdown (.md), text (.txt) or CSV (.csv) file. Only those kinds: a photo or PDF shown to you in chat cannot be passed on as bytes, and for those the answer is the ticket's link so the person can add the file in the app.

Attach a photo or PDF the person added to this chat onto a ticket. Pass the file itself as file. This works only where the chat app hands the file to the tool, as ChatGPT does; anywhere else, or for another kind of file, the answer is the ticket's link so the person can add it in the app. For something you wrote, use attach_file.

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.

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.

Add text to the end of a ticket's description, after a blank line. Nothing already there is changed, including an edit someone made a moment ago, and the description is not resent. Use this to add notes, findings or a plan below what a person wrote.

Move a ticket forward one step at a time: unprioritized → prioritized → started → finished → delivered. Give a ticket points with update_ticket before starting it. Finished is the last step you take on your own; deliver only when the person asks. Cancelled is reachable from any open state and needs a resolution. To move a ticket back to the Icebox or the Backlog, tell the person where it is going, then use update_ticket with state. Accepting or rejecting is a person's decision, made in the app, so this tool offers neither.

Add a comment to a ticket. Supports @mentions. 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.

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.

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.

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.

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.

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

Add a step to the end of a ticket. Place it elsewhere with move_subtask. Steps someone performs are subtasks, one action or command each, not checkboxes in the description.

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.

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

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

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.

Record that a ticket waits on another ticket, a project, or an outside event (External). Add one blocker per condition that clears on its own, each with a short title. A blocker with a date says only its date condition, not the other blockers.

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

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

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.

Start a project: a name, and the description where its plan lives. It lands at the end of the list; the person orders projects in the app.

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.

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

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

Takes no parameters.

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.

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 the labels on the board, with the ids that label_ids takes.

Create a label the board does not have yet, such as "fundraising" when tagging asks for one that is missing. Use it only when the person asks: a board's labels are its own vocabulary, and a near-duplicate splits every later filter. A name the board already has, in any case, is refused with the existing label.

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.