Structure of the component library
🟥 Structure of the "Component library" page
This text is a reference. What types of text are there?
The component library is used to define, organize and manage reusable modules for projects. It enables a standardized structuring of projects by storing individual work packages, checklists or acceptance criteria centrally and using them in different projects.
Two different views are available within the component library:
- Grid view - a tabular overview of all existing components
- Tree view - a hierarchical structure for the detailed organization of project components
The grid view - quick overview
In the grid view, the components are listed in a table. This view is particularly suitable if many components are managed and a quick search or filtering is required.
The table contains the following columns:
- Name - the name of the component
- Sub-elements - number of parts contained within the component
- Tags - When work packages of a component are converted into tickets, they automatically receive the assigned tags. This simplifies the subsequent sorting, assignment and prioritization of the tickets.
The filter function makes it possible to search for specific components or to narrow down the list using relevant criteria.
The tree view
The tree view shows the components in a hierarchical structure. Complex projects can be modeled here by nesting sub-elements.
Each component can be expanded to display its individual building blocks. New components can be created directly within an existing component by using the plus symbol next to the name.
Types of components in the component library
Four different types can be used when creating new components:
- Epics - Large, superordinate sections of a project that comprise several work packages
- Work packages - Concrete tasks that are later converted into tickets
- Checklists - A collection of to-dos or information that must be processed either internally or by the customer
- Acceptance tests - Definitions for checking whether a specific work result meets the requirements
Create new components
New components can be defined using the "Add component" button. Each component contains the following information:
- Icon - A visual symbol for quick identification
- Name - The title of the component
- Description - A public statement describing the purpose of the component
- Tags - For categorization and automatic labeling of tickets created from the component
- Internal note - Non-public information or instructions for implementation
Using the components in projects
The components created in the component library can be integrated into projects and used as the basis for tickets. This creates a standardized and reusable structure that makes the project process more efficient and enables better traceability. All tickets generated from components are automatically integrated into the regular Leadtime project structure.