You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey Community 👋,
I am looking for a way, to prevent Tempo from overbooking time, that was "sold" to the customer.
Looking at contract types like lump sum (Pauschale), cost reimbursement (fixes Kontingent) or time and material (Zeit und Aufwand) as the exemplary business cases.
In some business cases like time and material or maybe lump sum too, it is allowed to overbook the initially estimated time, that is sold to the customer.
In other business cases, where a certain amount of time is sold to the customer and must not be overbooked at all, like cost reimbursement, you want to prevent Tempo to overbook it.
This must be a general problem for all contractors, working in an ERP environment, where the systems are integrated with each other.
How did you solve this problem, when working with Jira and Tempo?
I am very happy, to learn from your experiences.
Kind regards, Alex