This video gives you an overview of the ticket system in Leadtime. You'll learn the connection between projects and tasks, why a ticket-based workflow is so valuable, and which views are available to you.
The basic principle is simple: Projects are containers, the actual work happens in tasks (also called tickets). Each task has a status, a responsible person, and time tracking. So you always see what's running, who's working on it, and how much effort has gone into it.
A ticket-based workflow solves five core problems: First, visibility – every task is a ticket, the whole team sees the status. Second, structured collaboration – discussions, decisions, and progress happen directly in the ticket with comments and attachments. Third, documentation and knowledge transfer – over time a central knowledge base develops, new employees get up to speed faster, and already solved problems don't need to be analyzed again. Fourth, no information loss – if someone is unavailable, someone else can take over seamlessly. Fifth, management and control – the combination of tickets and time tracking gives you an objective, data-driven control tool in real time.
Leadtime offers two main views: the List View as a tabular view with filter, sort, and search functions, and the Kanban Board with columns per status and drag-and-drop. Both views can be saved with filters and called up with one click.
In the ticket detail view you find the title, description, a chronological thread for collaboration, and metadata like project, type, status, assignment, estimate, deadline, and time bookings – the foundation for billing and analysis.
In the last videos you built the basic structure. Internal projects for self-organization, external projects for your customers.
Now it's about how you work with these projects. And that happens through the ticket system.
In this video you get an overview of the ticket system in Leadtime. You'll learn the connection between projects and tasks, why a ticket-based workflow is so valuable and which views are available to you.
I'm showing a diagram now.
You see a project at the top. In this example it's the marketing project. Below you see five tasks. These are individual tasks within the project: Create advertising material, maintain website, write blog, plan newsletter, produce videos.
That's the basic principle: Projects are containers. The actual work happens in the tasks.
Each task has a status. New, in progress, done. So you can see at a glance what's running and what's finished.
Each task has a responsible person. Someone who takes on or coordinates the task.
And each task has time tracking. Whoever works on a task books their time directly to that task. So you see exactly how much effort went into a task.
In Leadtime we also call tasks tickets. It's the same thing.
Now you might wonder: Why do I need this?
Because work quickly ends in chaos without structure. Requests come via messenger, email, in meetings. Important information disappears in chat histories. Nobody knows what's currently happening. Employees are constantly interrupted because they're waiting for follow-up questions.
A ticket system creates order. Fundamentally.
First: Visibility. Every task is a ticket. Everyone on the team can see what's running, who's working on it and what the status is. No more uncertainties.
Second: Structured collaboration. Discussions, decisions and progress happen directly in the ticket. All information is in one place. Comments, attachments, time bookings. Nothing gets lost.
Third: Documentation and knowledge transfer. Every ticket is a complete process with history. Over months and years this creates a central knowledge base. New employees can get up to speed faster. Customer questions are easy to answer. And already solved problems don't need to be analyzed again.
Fourth: No more information loss. If someone is on vacation or sick, someone else can take over seamlessly. Because everything is documented in the ticket.
Fifth: Management and control. The combination of tickets and time tracking gives you an accurate real-time overview. How much work is in which project? Which tasks are overdue? Who is overloaded? You get an objective, data-driven control tool.
In Leadtime the ticket system is directly integrated. You don't need an additional tool. Everything in one place.
I'm opening a project now and showing you the two main views.
First the List View. This is the tabular view. You see all tasks in a list with all important information. Status, responsible person, deadline, time spent.
This view is perfect when you have many tickets. You can filter: Show me only open tasks with high priority. You can sort: Show me the oldest tasks first. You can search: Where's the ticket about the login problem?
At the top you see Quick Search for a quick search. Then Add Filter for detailed filtering by status, type, responsible person and more. With the gear icon you can show and hide columns.
Now I switch to the Kanban Board. I click the gear icon and switch the view.
In the Kanban Board you see columns. Each column is a status. New, In Progress, Feedback, Done.
The tasks are cards that you can move between columns by drag and drop. When you drag a task from New to In Progress, the status changes automatically.
The Kanban Board is visual and very intuitive. You see at a glance where each task currently stands. It's perfect for agile teams and for everyone who works visually.
The nice thing: You can save both views. You can save a filtered List View, for example "My open tasks with high priority". And then call it up with one click every morning.
When you open a ticket, you see the detail view.
At the top left is the icon and title of the ticket. Below comes the description. Here it says what it's about. What's the problem? What should be achieved?
Below you see the thread. It's like a forum. Team members can write comments, ask questions, document progress. Everything sorted chronologically.
On the right side are the metadata. Project: Which project does the ticket belong to? Type: Is it a feature, a bug, a management task? Status: Is it new, in progress, done?
Assigned to: Who's currently working on it? Responsible: Who's overall responsible? Estimate: How long will it take? Due date: When must it be finished?
And very important: The time bookings. Here you see who worked when and how long on this ticket. This is the basis for billing in external projects. And the basis for analysis in internal projects.
You now have an overview of the ticket system.
You understand the connection between projects and tasks. You know why a ticket-based workflow is so valuable. And you know the most important views.
In the next video we'll look at how you create and edit tickets.
See you there!
