Skip to content
Docs · Board and tickets

Board and tickets

Board and tickets

A ticket is a brief an agent can pick up and a record of what happened. Create it through MCP from Claude Code; comment, assign and move it on the board.

Updated

On this page

The board is where work lives, for people and agents alike. Open Board in the left rail.

A ticket is two things: a brief someone (often an agent) can pick up, and a record of what happened to it. People decide and review; agents do the work.

Tickets are created through the MCP server: ask Claude Code, Codex, Cursor or another connected tool, or let an agent add them. The board has no Add ticket button. It’s where you comment on tickets, assign, move and edit them; your connected tool can do all of that too, with the same rules.

Boards and teams

A workspace has teams (people and agents; someone can be on several) and boards. Each board belongs to a team, or to the whole workspace. No team or board is special.

A new workspace starts with one team named after the workspace (say, “Acme”) with only you on it, and one board called “Board”, so the board menu lists “Board” under “Acme”. People who join later aren’t put on a team: they join the ones they work with.

Board opens the first board of a team you’re on, then a workspace-wide board. If there’s neither, it says so, with Create a board for owners and admins. The board’s title is also the switcher: click it (“Sprint 16 ▾”) for a menu of the workspace’s boards, grouped by team with workspace-wide boards last and a check on the one you’re on. Type in Find a board to narrow it down (a board’s name or its team) and press Enter to open the first match; Manage boards in Settings at the bottom opens Settings → Team. With only one board the title is plain text. Beside the title are the board’s team and how many tickets are open, then the search box and, at the right, the person filter (Everyone, Mine, faces, Unclaimed). Under it, one line holds the board’s description.

Managing teams and boards

Everything is in Settings → Team, below the people:

  • Teams lists each team with who is on it, its channel and its boards. Anyone can Join or Leave a team. Owners and admins also get a ⋯ menu: Rename, People and agents (who is on the team), New board for this team, Create team channel or Link a channel… (or Unlink channel) and Delete team. Deleting a team asks first; nobody leaves the workspace, no tickets are deleted, its boards become workspace-wide and its channel is archived.
  • Boards lists the active boards with their keys. Owners and admins create one with New board (for a team, or workspace-wide; the Key fills in from the name as you type, and you can change it) and use ⋯ to Rename or move (name, key, a one-line description, and its team) or Archive it.
  • An archived board is left out of the board menu and from connected tools’ board list. Its tickets are kept, and the board stays readable at its address. Unarchive brings it back (under Archived in the Boards list).

Names are 1 to 40 characters on one line, and unique in the workspace (ignoring case). Members see the lists read-only, apart from joining and leaving teams. Every change by an owner or admin is written to the audit log (a board’s description by its length only); joining or leaving a team yourself isn’t. Open boards pick up renames and moves at once.

Ticket ids and board keys

Every board has a key, and its tickets are numbered on it: on a board with the key YOM they’re YOM-1, YOM-2 and so on, like Jira. A key is 2 to 6 letters or digits, starting with a letter, and unique in the workspace. New board suggests one from the name as you type (Issues → ISS, ScreenApp → SA, Sprint 16 → S16), with a digit added if it’s taken, and shows what the tickets will be called (“Tickets will be ISS-1, ISS-2…”). Type your own and it stays. A new workspace’s first board, “Board”, takes its key from the workspace’s name (Acme → ACM).

  • Moving a ticket to another board gives it the next number there (YOM-12 → SA-4).
  • Changing a board’s key (⋯ → Rename or move) keeps every ticket’s number under the new key (SCR-4 → SA-4).
  • Old ids keep working, forever. Links, ?ticket= addresses, notifications, blockers and your connected tool all find a ticket by any id it has had. Opening an old link shows the ticket under its current id and puts that in the address; the ticket’s header says Previously YOM-12.

Before board keys, ids were workspace-wide (TKT-13). Every ticket kept its number and took its board’s key (TKT-13 on the Yomenie board is now YOM-13), and TKT-13 still works. TKT itself can’t be a board’s key. Key changes are in the audit log.

A team’s channel

Every team can have its own channel, so you can talk to the team without making one by hand. New team has Also create #platform (the team’s name as a channel name), ticked. The channel is public, and its topic says whose it is.

  • The name is the team’s address. The channel is always named after the team: renaming the team renames the channel, and renaming the channel (in its settings) renames the team. Only owners and admins can rename a team’s channel, since it renames the team too. If another channel already has the name (archived ones count), the team isn’t created or renamed: link that channel instead (Link #platform instead in the dialog), or pick another name.
  • People follow the team. Joining a team, or being added to it, puts you in its channel; leaving it, or being taken off, takes you out. Agents on the team too. Leaving the channel doesn’t take you off the team. The last person in the channel stays in it.
  • Existing channels. Link a channel… makes an existing public channel the team’s channel and adds the team’s people and agents to it. If its name isn’t the team’s, the dialog says it will be renamed. #general and private channels can’t be linked, and a team’s channel can’t be made private.
  • Archiving and unlinking. Archiving a team’s channel unlinks it (unarchiving doesn’t link it again). Unlink channel keeps the channel and everyone in it. Deleting the team archives its channel, never deletes it.

The channel’s About says “Team channel for Platform”. Links, unlinks and the membership changes an owner or admin makes are in the audit log; joining or leaving a team yourself isn’t, and neither is the channel change it brings.

Columns and order

A board starts with four columns: Backlog, In progress, Review and Done. There’s no priority field: the top of a column goes first. Drag cards up and down to order them, or across to move them. Lists over the API and MCP come back in the same order.

Each board can have its own columns. There’s no settings screen for them: ask your AI tool, as an owner or admin. “Add a QA column before Review on the Platform board, and make it a review column”, “Rename In progress to Building”, “Remove the Review column, move its cards to Done”. The board shows whatever columns it has, scrolling sideways when there are many (up to 12). A few rules hold whatever the columns are called:

  • New tickets go to the bottom of the first column, unless the tool names a column (or to the backlog list, when the board has it on: below).
  • The last column is Done: tickets there count as done (metrics, unblocking, newest first). Move a column to the end and it’s Done from then on.
  • A review column (marked with a small review tag) asks a person to look when a card lands there (below). Any number of columns can be review columns.
  • Removing a column moves its cards to the column on its left (the new first column, for the first), unless you say where. Nobody is notified for those moves.
  • Taking a ticket puts it in the working column: the first column after the first that isn’t review or Done (In progress on a new board).

Column changes are in the audit log and show on open boards at once. Boards from before custom columns are exactly as they were.

A ticket moved to another column without a place (from the detail, a card’s menu or update_ticket) lands at the top, except in Backlog, where it goes to the bottom.

Done is newest first: the ticket that got there last is on top. Its order is the time each ticket moved to Done, so cards in Done can’t be dragged up or down, and a card dropped anywhere in Done goes to the top.

The backlog list and its line

A board can trade its Backlog column for a ranked backlog list with a line for what’s next. It’s off until an owner or admin asks their AI tool (“Turn on the backlog list for the Platform board”), and comes on by itself with sprints. Turning it on makes the Backlog column’s cards the list, in their order, and the column goes; turning it off puts them back in a first column called Backlog. Turning sprints off leaves it on.

The list sits at the left of the board, a little wider, with dashed cards: the top is what’s next. New tickets land at its bottom. The arrow in its heading folds it into a narrow strip, and the board remembers that in your browser. When a sprint ends, or one starts empty, it opens once by itself; fold it again and it stays folded.

A dashed amber line splits what’s next from what’s later. With cards above it, its pill says how much: Up next · 3 cards · 8 pts, or Next sprint · … with sprints on, and cards below it are lighter. With nothing above it, it just says “Drag cards above this line for what’s next”. Drag cards up and down, across the line, or drag the line itself.

Under the line, Move these 3 to In progress (the board’s first column, by name) moves everything above it there, in order, in one go (into the sprint, with sprints on). Grooming is ticket work: any member can do it, and so can their AI tool: “Groom the Platform backlog: put the most urgent first and about 20 points above the line”, then “Move what’s above the line onto the board”.

Sprints

Boards are plain Kanban by default. Sprints are turned on, off and sized through your AI tool, as an owner or admin: “Turn on two-week sprints for the Platform board”. Sprints turn the backlog list on (above). With sprints on:

  • A sprint is either running or not. At the right of the board’s title it reads Sprint 17 · ends Fri · 12 of 20 pts (points in Done, of the sprint’s total; no points part while it has none) with End sprint, or No sprint running with Start sprint. On a phone it wraps under the title.
  • Start sprint opens a small dialog: “Start Sprint 4”, its length (the board’s, changeable for this sprint) and end day, and who joins: the cards above the backlog line plus any carried over (“5 cards, 18.5 pts will join”). With nothing to join it warns “Sprint 4 will start empty”, and starts anyway if you go ahead.
  • The columns show the running sprint’s cards. With no sprint running they show the cards waiting for the next one (carried over, or put on the board meanwhile), the backlog opens by itself, and the button under its line reads Start Sprint 4 with these (it opens Start sprint). An empty running sprint says so in its first column (“Sprint 4 is empty. Drag cards from the backlog.”).
  • Dragging a card out of the backlog onto a column puts it in the sprint (or, between sprints, in the next one); dragging one back takes it out.
  • End sprint asks one question: put the cards that aren’t done back in the backlog (just below the line) or keep them on the board for the next sprint, and previews it (“4 unfinished cards go back to the backlog.”). It doesn’t start the next sprint: the board says No sprint running until someone starts it. Done cards stay with the sprint that ended.
  • Turning sprints on doesn’t start one either: the open cards on the board wait for Sprint 1.

Any member can start and end sprints and move cards in and out (from the board or their tool: “Start the sprint”, “End the sprint, unfinished to the backlog”, “Put YOM-12 and YOM-14 in the sprint”). Turning sprints off ends the running sprint, and the board shows every card again. Sprint settings and every ended sprint are in the audit log. There’s no planning screen, sprint goal or velocity chart.

Big boards

Boards can hold thousands of tickets, most of them in Done, and the board never loads them all at once. The board fills the screen under its title, search and filter, and each column scrolls on its own with its name and count staying in view. Each column shows its first 30 cards and loads the next 30 as you scroll near its end; there’s no button, just a “Loading more…” placeholder while they come. The number beside each column’s name is always the full count (1,284), not just what’s loaded. Dragging, quick assign and live changes work on loaded cards as usual: a card that moves into a part of a column you’ve already scrolled through shows up in its place, and one that lands further down appears when you scroll to it.

The search box beside the board’s title (Find a ticket: key, title or label) finds any ticket on this board, however old, Done included. Type a ticket’s id (YOM-12, or any id it had before, like TKT-12) to find exactly that ticket, or words from its title or label. The matches replace the columns as a short list (id, title, column and who has it); click one, or press Enter on it, to open it. More load as you scroll. The search is in the address (?q=login), so you can share it. Esc or × clears it and brings the columns back.

Your connected tool searches the same way, with search_tickets (see Through MCP).

On the card

A card shows the id, label, title, who has it, a red Blocked mark while it waits on an unfinished ticket, a small link count, and points if it has any (shown as typed: 0.5, 1.5, 3).

Standups go through the board together, so the common changes work on the card itself:

  • Assign: press the face (or “Unclaimed”). Type to filter; Me comes first, then the people in your conversation on the floor, then everyone, and Unassign at the end. One press saves.
  • Card menu (⋯): Open, Assign…, Comment…, Move up, Move down (not in Done, which keeps its own order) and Move to each other column (and the backlog list, when it’s on). It works from the keyboard: Tab to the ⋯ button, Enter, arrows.
  • Comment… opens a small box. Enter posts; Shift+Enter is a new line.
  • Drag: with the pointer or touch, or Tab to a card’s grip and use the keyboard.

Filter by person

The faces above the columns show whoever has a card on this board. Press one (or several) to see only their tickets, Mine for yours, Unclaimed for nobody’s, Everyone to clear. The column counts follow the filter, and the columns load only the matching tickets. The filter is in the address (?who=priya), so you can share it, and this browser remembers it.

The ticket

Open a ticket by clicking its card (or Enter). The address gets ?ticket=YOM-142, so you can link to it. In it:

Part Notes
Title Up to 200 characters
Description The brief, in markdown, up to 20,000 characters. Write what and why, then Done when as a checklist (- [ ] …). Tick a box to mark it done; the description says “2 of 4 done”. Edit and Preview while writing
Column, assignee A person, an agent, or nobody. Take it assigns it to you and moves it to In progress
Label Optional, up to 24 characters
Points Optional: 0 to 100 in steps of 0.1, so 0.5 and 1.5 work (0 means not sized). Type a number or pick 0.5, 1, 2, 3, 5, 8 or 13 from the menu beside the field. The board doesn’t ask for it
Blocked by Tickets this one waits on, by id or words from the title. Lists what it blocks too
Links The MR / PR, the branch and, once it ships, the release
Activity Comments and what happened, newest at the bottom

Changes made by anyone else show up in an open ticket at once.

Blocked by

A ticket can wait on others in the same workspace, on any board. It can’t wait on itself, and no loops: if YOM-9 waits on YOM-12, YOM-12 can’t wait on YOM-9 (or on anything that waits on YOM-9). Up to 20 per ticket.

While any of them isn’t done, the card shows Blocked. Taking a blocked ticket still works: the app asks you to confirm first, and over MCP claim_ticket claims it and returns a warning naming the open blockers. When the last blocker moves to Done, the person the ticket is assigned to gets a notification (“YOM-139 is unblocked”).

Each link has a kind: MR / PR (GitLab and GitHub alike), Branch, Release, Doc or Other, an https:// address and an optional short title like !412 or v1.4.0. Up to 20 per ticket. Yomenie never opens or fetches them; they’re shown as you gave them.

Activity

One timeline per ticket: comments from people and agents (markdown, like chat) and events in between: created, moved, assigned, title or description edited, blocker added or removed, link added or removed, and where the ticket was mentioned. Events never repeat the text that changed. Comments and changes made through a connected app say so: “Priya · via Claude Code”. Show older pages back.

Refer to tickets, channels and people

In a description or a comment, write another ticket’s key (YOM-12, or any id it had before) and it becomes a chip with its title and a dot in its column’s colour; hover for the board, status and assignee, click to open it. #platform links a channel and @Priya mentions someone, as in chat. Type # for a list of channels and tickets, and @ for people, AI teammates and teams. In Edit, references show as you’d type them; they’re saved as links that follow renames and new keys. Mentions in ticket comments don’t notify anyone yet.

When a ticket is mentioned somewhere else, its activity says so: “Mentioned in YOM-14 by Priya”, or “Mentioned in #platform by Priya (see message)”. One line per message or ticket, however often it’s edited. A line from a conversation shows only to people who can read that conversation. A ticket you can’t see shows only its key, unlinked.

Review goes to a person

There’s no reviewer field. When a ticket assigned to an agent moves into a review column (Review on a new board), the agent’s manager gets a notification (“YOM-142 is ready for review”), unless they moved it themselves. When a connected app moves a ticket assigned to you into Review (Claude Code finishing work for you), you get one too. Both kinds can be turned off under notifications.

Through MCP

Connect Claude Code (claude mcp add --transport http yomenie https://yomenie.us/mcp, then /mcp → Authenticate) and ask in plain words: “Create a ticket on the Platform board: fix the flaky login test”, “What should I work on next?”, “Claim it”, “Comment on YOM-142 that the fix is in !412”, “Attach the MR https://gitlab.com/…/merge_requests/412”, “Move it to review”. “Find the ticket about invoice reminders” or “What did we finish this week?” use search_tickets, which pages through any number of tickets. Behind those it uses create_ticket, next_ticket, get_ticket, claim_ticket, comment_on_ticket, add_link, set_blocked_by and update_ticket; for the board itself get_board, update_board (columns, sprints), set_backlog_line, move_above_line, end_sprint, move_to_sprint and move_to_backlog (all the tools). A new ticket goes on the board you name; your tool can leave the board out only when the workspace has exactly one active board, otherwise it’s told which boards to pick from. Codex, Cursor and other MCP clients connect too: see Connect your tool.

The board has the command too, with a Copy button and a few things to ask. Until you’ve connected a tool to the workspace, the line under the board’s title (after its description) says “Tickets come from your AI agent. Ask it to create one, then comment, assign and move it here.” with a Connect Claude Code or Codex → link that opens it. Once you have, it names your tool and suggests something to ask, such as “Take the next ticket, do it and move it to Review”, with More prompts → linking to Work through your AI agent. × hides the line in that browser (closing the “connect” line doesn’t hide the tip you get once connected). Once it’s hidden, the same setup is at the top of Settings → Connected apps.

Every member can change tickets (the tickets:write action). Changes to tickets are written to the audit log; comments live on the ticket.

Agents and leases

When an agent takes a ticket, it holds a lease for a set time (30 minutes by default, up to 4 hours). While the lease is live, nobody else, person or agent, can claim that ticket, so two never work on the same one. Claiming assigns the ticket to the agent and moves it from the backlog or the first column to the working column (In progress). A paused agent, or one without the “Claim a ticket on a lease” scope, can’t claim. Agent permissions.

Live updates

When a ticket changes, in the app, from a connected tool or by an agent, every open board updates for everyone at once (the changed cards and the counts), and so does an open ticket and an open search. Nobody needs to reload.