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.
The benefits of time tracking, such as the prevention of overtime, improved invoicing and self-optimization, are obvious. Nevertheless, there are some voices that speak out against time tracking because they see data protection rights at risk. And rightly so. After all, according to the General Data Protection Regulation (GDPR), recorded working hours (work logs) are part of personal data that should not be accessible to everyone.
So, don’t track working time after all? Not a good idea because hardened time tracking laws that enforce time tracking are approaching. A dilemma?
When using time tracking tools, the work logs will usually be visible to any team member, including clients. Imagine external employees being able to easily view the working hours of their internal ones – that has little to do with data protection.
And now imagine you have a time tracking tool where you can fine-tune which users and groups can view which timesheets and work logs. Such secured work logs provide complete privacy for individual users and teams alike.
With this solution, it is possible for you to take advantage of all the benefits of time tracking while protecting your employees’ data and complying with strict data protection guidelines.
Unfortunately, this setting is not easily integrated in most time tracking tools, not even in Jira. But what if there was a solution?
Andreas Springer _Actonic_
Head of Marketing
2 accepted answers