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
Next: Root
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 there,
I just want to collect some hints about logging my work. Our company uses time tracking, we log our work on Jira issues which can be challenging when you do general activities like following the community, reading announcements, overviewing product stats, and checking competitors.
We created a few "container" issues where we can log meetings and other activities, but I don't find this effective.
Any best practices out there?
I don't know if you use Tempo to track your time, but their best practice is using so-called "internal issues" for these:
https://www.tempo.io/blog/2016/manage-and-track-internal-work-with-internal-issues
So, pretty much what you're doing already.