Adapt the ticket system to your workflows
🟨 Overview of the customizing options of the Leadtime ticket system
This text is an overview of topics. What text types are available?
Leadtime's ticket system offers a wide range of customization options so that it can be optimally adapted to a company's workflows. This flexibility is particularly useful for increasing efficiency in specific work processes.
You can find all customizing options for tasks under Administration / Task settings.
This overview presents the main components of customizing.
Task types
Types of tasks that are to be processed with the ticket system. By default, types such as "Features" and "Bugs" exist, as Leadtime is often used in software development companies. "Features" refer to value-adding activities such as the development of a new product or feature, while "bugs" describe the elimination of problems.
New types can be added to these standard task types. These new task types can have individual status characteristics, their own activities and suitable user-defined fields.
Task status
These statuses indicate the progress of a task or ticket. By default, there are statuses such as "New", "In progress", "Feedback", "Completed", "Closed" and "Backlog".
Work activities
This component refers to the time bookings for tickets. For example, a developer would book their time for the activity "Development", while a project manager would book for "Management". Custom activities can be added to better reflect specific workflows.
Custom fields
These fields can be created to capture specific information about a task type that is not covered by standard fields. This customization provides more flexibility to tailor the tasks to the company processes.
Task templates
A task template is a ready-made template for tasks or tickets in a project management or ticket system such as Leadtime. It is used to create recurring tasks quickly and in a standardized way without having to enter all the details manually each time. This saves time, ensures consistency and ensures that all relevant information is captured for a particular type of task. Ticket templates are an excellent input aid for guest users. For example, you could create a template for "bugs". When customers want to report a bug, a task template provides a template for what data they need to enter so that the developer can reproduce the bug as quickly as possible.