This video walks you through a complete ticket workflow in Leadtime – from task assignment to completion. Using a concrete scenario, you see how two team members collaborate through a single ticket: Marc from sales asks his colleague Sonja from marketing to create a customer presentation.
First, you see how Marc creates a ticket using the editor. The editor offers various block types via slash commands, including headings, bullet lists, tables, images, and code blocks. Especially useful: the built-in AI assistant. Marc selects his draft text and has the AI generate a complete, structured task description – with context about the meeting, expectations for the deck, and details about individual slides.
Next, you learn how metadata makes a ticket manageable. Project, type, status, assignment (Assigned to and Responsible), estimated effort, and due date – all of this ensures everyone on the team knows who needs to do what by when. The "Assigned to" field is the key mechanism for handovers between team members.
Sonja then demonstrates what working on a ticket looks like: status updates, comments with progress reports, mentions for direct communication with colleagues, file attachments, and time tracking. Everything is automatically documented in the ticket's history – a complete chronological record of collaboration.
Finally, Marc reviews the result, gives feedback, and closes the ticket. You've now seen a realistic end-to-end workflow and understand how the editor, AI assistant, status changes, and assignments work together in Leadtime.
In the last video you got an overview of the ticket system. You know the views, you know why a ticket-based workflow is so valuable.
Now it gets practical. In this video you see a complete workflow from start to finish. And along the way you'll learn about the editor and the AI assistant.
The scenario: Marc Schmidt is head of sales and has an important customer meeting. He needs a presentation. So he assigns his colleague Sonja Berg from marketing to create the deck.
We follow the ticket from assignment to completion.
Marc opens the internal project Sales. This is where all sales-related topics run.
He clicks Add Task.
The dialog opens. Marc chooses a presentation icon and writes the title: Customer presentation for TechCorp meeting.
Now comes the description. And here I'll show you the editor.
Marc clicks into the text field and types slash. A menu opens with all available block types. Heading, Bullet List, Table, Image, Code and many more.
Marc chooses Bullet List. He enters a few bullet points:
Company introduction. Product overview with features. Pricing and packages. Success stories. Next steps.
Below he writes: Meeting is on Friday with the CTO of TechCorp.
So far so good. But Marc wants to elaborate the description.
Marc selects all the text. Then he types slash and chooses Generate with AI. You can also use Command G.
A prompt field opens. Marc writes: Create a clear task description for a colleague who should prepare a customer presentation.
The AI generates a complete text. Structured, clearly written, with all important details. Context about the meeting, expectations for the deck, the individual slides.
Marc accepts the text. That was quick.
Now Marc fills in the metadata. On the right in the sidebar.
Project is Sales. That's already preselected.
Type: Management.
Status: New.
Assigned to: Sonja Berg. This is important. This way Sonja knows she's up.
Responsible: Marc Schmidt. He's responsible for getting this topic done.
Estimate: Six hours.
Due date: Thursday. One day before the meeting.
Marc clicks Create and open. The ticket is created and opens directly.
We switch to Sonja's perspective.
Sonja sees the ticket in her task list. It's assigned to her, status New.
She opens it. Reads the description. All clear, she knows what to do.
She scrolls down to the comment field.
Sonja writes an update. She types: I started with the presentation. Here's the current status.
Then she types slash and chooses Bullet List.
Company introduction done. With checkmark.
Product overview with screenshots inserted. With checkmark.
Pricing section in progress. With hourglass.
Then she wants to ask Marc a question. She types at and then Marc Schmidt. A mention. Marc will be notified.
She writes: Do you need the current prices or the new ones?
The toggle is set to Internal. That fits because it's an internal project.
Sonja clicks Update. The comment appears in the history with timestamp.
Sonja now changes the status. She clicks on New and selects In Progress.
The status change appears automatically in the history.
Now she books time. She clicks the Time Tracking button in the top right.
Three hours. Activity: Management. Book.
The time booking also appears in the history.
The next day Sonja is done.
She opens the ticket again and writes a final comment: Presentation is ready! All slides are in SharePoint.
She types slash, chooses File and attaches a PDF preview.
Now she changes the status: In Progress to Feedback.
And very important: She changes Assigned to to Marc Schmidt. The ticket goes back to Marc.
She books another three hours. Update and close.
Marc sees the ticket back in his list. Assigned to him, status Feedback.
He opens it. And sees the complete history. The original description. Sonja's updates. The time bookings. Six hours total. The file attachment.
Marc writes: Perfect, thanks! Presentation looks great. With thumbs up.
Then he changes the status: Feedback to Done.
The ticket is completed. In the project list it now appears under Closed Tasks.
You've now seen a complete ticket workflow. From assignment through processing to completion.
You know the editor with its slash commands, block types, mentions.
You know how the AI assistant helps you generate and improve texts.
And you've seen how status changes and assigned to work for handovers.
In the next video we'll look at the customizing options. How you create your own task types, statuses and templates.
See you there!
