Mention @Trundle in any channel it's been invited to, or in a direct message, and describe what you need in plain English. Trundle reads the surrounding conversation for context and can:

create a ticket from your request,
answer a question about your project data,
answer a question about your codebase, or
ask you for clarification when a request is ambiguous.

If a ticket request could belong to more than one project, Trundle posts a project picker ("Which project should I create this ticket in?") so it's filed correctly.

Permissions

Connecting Slack requires the Manage Integrations permission. During setup, the Trundle Slack app requests access to read channel history so it can use conversation context. Trundle only processes conversations where it's explicitly mentioned, or channels it's been formally invited to; it does not read your whole workspace.

How a ticket's origin is tracked

Every ticket records where it came from, for example whether it was created manually, auto-generated by Trundle, created from Slack, or produced by a quality-benchmark run. This origin is stored on the ticket for traceability and reporting. (It's used internally for context; it isn't currently displayed as a dedicated field in the ticket view.)

Knowledge-grounded answers

When Trundle answers a data or code question from Slack, it retrieves the most relevant material from your account and project Knowledge Base, so answers are grounded in your own documentation.

FAQ

Who can connect Slack?

A user with the Manage Integrations permission connects and authorises the Slack app for your workspace.

Can Trundle read all of our Slack messages?

No. Trundle only processes conversations where it's explicitly mentioned, or channels it has been invited to.