Tickets and the AI
The ticket providers are available to the AI as MCP tools in every chat session. Requests like "show the open bugs", "read PROJ-123 before you change the function" or "create an issue for this crash" work without copying keys.
Reading
The reading tools work in every session mode.
| Tool | Returns |
|---|---|
tickets_providers | The configured providers. |
tickets_search | Tickets matching a query. |
tickets_get | One ticket with description. |
tickets_transitions | The status transitions allowed for this ticket in its current status, with the fields each transition requires. |
tickets_create_meta | Projects, issue types and required fields for creating an issue. |
tickets_edit_meta | The editable fields of a ticket. |
tickets_templates | The ticket templates of the exploration. |
tickets_children | The tickets under a parent, for work packages. |
Which transitions exist is configured per project in Jira. Tracemoor does not model the workflow. It asks the ticket.
Writing
A write needs two things:
- The session runs in Brave mode. In ReadOnly and Safe the write tools are refused, and the AI can ask you to switch. See Session modes.
- You approve the preview. Before every write, a dialog shows what will change. Approve runs the write, Reject or closing the dialog cancels it. Without a dialog, for example in a headless run, nothing is written.
| Tool | Effect |
|---|---|
tickets_create | Creates an issue, optionally from a template. |
tickets_update | Changes title, description or fields. Only the fields named in the call are touched. |
tickets_transition | Changes the status, by transition ID or by target status (to_status). If no transition leads to the status, the error lists the reachable ones. |
tickets_comment | Adds a comment. |
tickets_assign | Assigns a person by name, email, me, or empty for unassigned. If the name matches several people, the call fails and lists them. |
tickets_set_parent | Sets the parent of a ticket. |
tickets_import_to_projectdocs creates or refreshes ticket entries for a
list of keys. It writes only into the exploration and shows no preview, but it
also needs Brave mode.
The AI handles several tickets one by one. Eight tickets mean eight previews.
The preview
The preview is a form. Fields the AI cannot know, for example a fix version, can be filled in or changed there. Required fields and the fields the AI set are at the top, the others under ▸ n more field(s). Approve stays disabled while a required field is empty or a heading required by the template is missing.
When the AI rewrites a ticket, the preview shows the current title and body next to the proposed ones.
After each write from the chat, the Tickets view reloads the affected tickets.