A project in Leadtime initially consists of components, epics and work packages. This structure provides an overview - but tickets are needed to turn planning into real implementation. Because only tickets can be

The following therefore applies: a work package is the template - the ticket is the task.

Leadtime offers several ways to generate tasks from a work package:

In the project tree, you will find a three-dot menu for each element (component, epic, work package). Click on "Create tasks" to create one or more tickets directly:

When you open a work package, you will find the "Create task" button in the right-hand sidebar. This creates a ticket for this one package only.

In the Configuration / Implementation overview submenu, all elements of the project are displayed in tabular form. The ticket linked to the element is displayed in the last column; if this does not yet exist, there is a "Create task" button here that creates the ticket.

When the ticket is created, it is automatically filled with the most important information from the work package:

The new ticket appears in the task area of your project - including ID, type, status, priority, assignment and deadline (optional).

While the work package is aimed at the customer, specifically the creation of the requirements specification, the associated ticket should be formulated in such a way that an employee can process it effectively.

The work package and ticket use the same pool of information. However, the information in the ticket is prepared differently. At the top, a specific task description for the responsible employee is generated via AI from all available information, but especially from the customer's answers to the questions in the question package.

For this reason, the ticket also contains the data from which this summary was generated. Specifically, the ticket is structured as follows:

Tags are a central element in Leadtime for categorizing and filtering tasks - especially in complex or multi-project environments.

When a ticket is created from a work package in the project tree, it automatically takes over:

These tags appear directly in the ticket and are also visible in the various planning tools - for example in the pipeline or in the big picture.

Tags create context without having to constantly open the project tree:

A ticket with the tags coach and coach_start belongs to the coach component and the epic "Start". This makes it immediately recognizable:

Customers can also be assigned tasks: As soon as they have access to the project as a guest user, tickets can be assigned to them. This is particularly useful for preparatory tasks such as a checklist.

In our workshop scenario , for example, the agency sends a checklist to the client right at the start of a collaboration. This is assigned to the client even before the project meeting takes place.

Especially in projects that build on each other, it is important that tasks are not processed in isolation. In Leadtime, you can therefore reference another task within a work package - e.g. if a task requires the result of a previous task.

A typical example: The "Create design" work package builds on the content from "Create content". A direct link to the upstream work package can be inserted in the description of "Create design". To do this, simply enter !Create content in the text or select the desired package via the slash menu. Leadtime automatically inserts a reference.

If a ticket is later generated from the work package, this reference appears directly in the ticket description. This provides context, avoids queries and improves the handover between team members.

This means that important connections are retained - even if tasks are completed in a different project module, team or time slot.

The implementation overview is the central management tool for projects in Leadtime. It displays all work packages from the project tree in a tabular overview and shows in real time:

The overview is therefore the most important control tool for project managers to keep track of complex projects - especially when customers and team members are working on tasks at the same time.

The implementation overview lists all components, epics and work packages of the project tree in a collapsible hierarchy. It offers the following columns:

The title of the respective element (component, epic or work package) from the project tree. The hierarchy is visible via collapse and expand functions.

Shows the progress within the work package. This is based on:

Example: A work package with 6 checklist items, 3 of which have been completed, shows "3/6" here.

Compares the booked time with the estimated effort:

So you can see at a glance:

The current status of the associated ticket - e.g. "New", "In Progress", "Feedback", "Resolved" or "Closed". This information comes directly from the task module and indicates how far the implementation has progressed.

Shows who is currently responsible for the task. If no ticket has been created yet, this field remains empty. For assigned tasks, the responsible user (internal or external) is displayed.