Crewboard

list_projectsread

List projects with their board type, lead, current on-call engineer, active sprint and members.

list_membersread

List workspace members with role, discipline, project membership, on-call duty and away/vacation status. Optionally only members of one project.

get_memberread

Get one member's profile (role, projects, on-call, away dates) plus their open assigned issues and workload.

get_workloadread

Workload per member: open story points assigned to them across all projects (anything not Done), with issue counts and availability. Optionally only members of one project.

search_issuesread

Search issues. All filters are optional and combine with AND. `query` matches every word against key, title, description and labels. Results are sorted by key.

get_issueread

Get an issue in full: description, status and how long it has been in it, links (blocks / is_blocked_by / duplicates / relates_to), epic or child issues, comments and change history.

list_sprintsread

List sprints with state (completed, active, planned), dates, goal and point totals. Only Mobile App (MOB) runs sprints; Web Platform uses a continuous board.

get_sprintread

Get a sprint with its issues and, per person, capacity, committed points (all issues in the sprint assigned to them) and remaining capacity.

list_labelsread

List labels in use with how many open and total issues carry each.

create_issuewrite

Create an issue. It starts in To Do with you as reporter. Optional assignee must be a member of the project; optional sprint must be an active or planned sprint of the same project (epics can't go in sprints).

update_issuewrite

Edit an issue's title, description, priority, story points, epic or labels. `labels` replaces the whole label set; `add_labels` / `remove_labels` change it incrementally. Use transition_issue for status and assign_issue for the assignee.

transition_issuewrite

Move an issue through the workflow: To Do -> In Progress -> In Review -> Done (In Progress can go back to To Do, In Review back to In Progress, Done reopens to To Do). Moving to Done needs a resolution; only In Review issues can be resolved as 'done', while wont_do, duplicate and cannot_reproduce can close any open issue. Starting work needs an assignee. Issues blocked by an unresolved issue can't enter review or be resolved as done. An optional comment is posted with the transition.

assign_issuewrite

Assign an issue to a member. The member must belong to the issue's project.

unassign_issuewrite

Remove the assignee from an issue.

add_commentwrite

Post a comment on an issue as yourself.

link_issueswrite

Link two issues. link_type is read from `key` to `target_key`: 'blocks' (key blocks target), 'is_blocked_by' (target blocks key), 'duplicates' (key duplicates target), 'is_duplicated_by', or 'relates_to'. Linking never changes either issue's status.

unlink_issueswrite

Remove the link(s) between two issues. With link_type (read from `key` to `target_key`), only that link is removed.

move_issue_to_sprintwrite

Put an issue into an active or planned sprint of its project, or back into the backlog with sprint_id 'backlog'. Epics and resolved issues can't be moved. The result shows the assignee's capacity in that sprint.

start_sprintwrite

Start a planned sprint. A project can have only one active sprint, so complete the current one first.

complete_sprintwrite

Complete the active sprint. Resolved issues stay in it; every unfinished issue moves to move_open_issues_to — a planned sprint of the same project, or 'backlog'. Required when unfinished issues remain.