Add meeting agenda item
add_meeting_agenda_itemAdd an agenda item to a meeting, optionally with notes, duration, and a linked work package. Use it to build or extend agendas and show discussions on work packages.
Instructions
Add one item to a meeting's agenda, optionally pinned to a work package.
Use it to build or extend an agenda: "add 'Release readiness' with 15 minutes", or "put #1234 on Thursday's agenda". Linking a work package is also how a ticket learns it was discussed — the link shows up on the work package's Meetings tab.
Returns the created item: {id, title, notes, duration_minutes, position, item_type, presenter, work_package, section, outcomes, meeting, created_at}. position is where
it landed in the agenda; items are appended to the meeting's last section.
Pitfalls. This needs the 'manage agendas' permission, so a 403 is about the account, not
the payload. A 422 usually means the work package is not visible to this account or the
meeting is already closed — violations names the attribute. The item's type is fixed
here: a simple item cannot become a work-package one later, because itemType is
create-only upstream.
Cross-references: get_meeting(meeting_id=...) to see the agenda you are appending to;
update_meeting_agenda_item to fix or reorder the item afterwards;
delete_meeting_agenda_item to remove it; add_meeting_outcome to record a decision
against it; list_meetings for the meeting id; search_work_packages for the work
package id.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | Markdown notes for the item. Omit for none. | |
| title | Yes | Agenda item title, e.g. 'Release readiness'. For a work-package item the UI shows the work package's subject instead, but a title is still accepted and stored. | |
| meeting_id | Yes | Numeric meeting id from list_meetings or get_meeting. The item is appended to that meeting's last agenda section. | |
| work_package_id | No | Work package to discuss under this item, from list_work_packages or search_work_packages. Passing it makes this a work-package item, which is what puts the meeting into that ticket's Meetings tab. It must be visible to this account. | |
| duration_minutes | No | Planned length of this item in minutes (0-1440). Omit to leave the item untimed; the meeting's own duration is unaffected either way. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Agenda item id (not the meeting id, not a work package id). | |
| notes | No | Item notes as markdown (raw); html is dropped. | |
| title | No | Item title. Empty for a work-package item, where the work package's subject is the title shown in the UI. | |
| meeting | No | Meeting the item was added to. | |
| section | No | Agenda section the item sits in, when the meeting uses sections. | |
| outcomes | No | Outcomes recorded against this item; always a list, empty when none. | |
| position | No | 1-based order within the agenda. | |
| item_type | No | 'simple' for a free-text item, 'work_package' for a linked one. | |
| presenter | No | User presenting this item. | |
| created_at | No | ISO 8601 UTC timestamp. | |
| lock_version | No | Optimistic-lock version. Echo it as update_meeting_agenda_item's lock_version so a concurrent edit fails loudly (409) instead of being overwritten. | |
| work_package | No | Work package this item discusses. Null both when none is linked and when the linked one is invisible to this account — 'notes' says when the latter happened. | |
| duration_minutes | No | Planned length in minutes; null when the organizer set none. |