Linking work packages
🟩 How to use the result of one work package in another work package
This text is a guide. What types of text are there?
Linking work packages: making dependencies transparent
Why links are important
In complex projects, many tasks are interdependent. A team member can often only start their work in a meaningful way if another team member has already delivered a result.
Example:
Before a designer can start with the layout, it must be clear what content should be on the page. The "create design" task therefore depends on the "create content" task.
To make such dependencies visible, traceable and transferable, Leadtime offers the option of linking work packages directly to each other.
This is how linking work packages works
The link is created via the description or internal note of a work package. You can place a direct link to another work package in the text - e.g. with the note:
Use the results of
Insert link
- Open the component in the component library.
- Edit the work package that is to link to another one.
- Go to the Description field.
- Type ! or select the element "Component element" via the slash menu .
- Search for the desired work package (e.g. "Create content") and click on it.
Leadtime now inserts a clickable link to the linked work package.
What happens when I use the component?
As soon as you use the component in a real project and tasks are created from it, the link is automatically included in the description of the associated ticket.
This means
- Team members immediately see which preliminary work they should include when they open the task.
- Links between tasks become transparent and traceable.
- Collaboration within the team is coordinated and efficient.
Best practices
- Always link when a work result is a prerequisite for the subsequent task.
- Clearly formulate in the description what exactly is to be used (e.g. "structure specification", "text content", "sitemap", ...).
- Use unique names for work packages so that they are easier to find when linking.
Conclusion: Context creates clarity
Linking work packages turns a loose collection of tasks into a structured, logically linked project:
- Dependencies are made visible
- Misunderstandings are avoided
- Project knowledge is transported to the right place