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.
My employer has purchased Tempo for our company.
From what I know of Tempo, it must be connected to an issue in order to track time.
This is a huge limitation for our company. We want to track time, but not everything we do is tied to an issue.
In my mind, it makes more sense to base the time tracking on the project (and then, maybe, an optional issue inside that project).
Because of this limitation, most of my coworkers have been using Toggl (it's just more flexible for non-issue issues).
With that said, how do you use Tempo when there's not an issue for the work needing to be done?
Example of work that would not be connected with an issue is phone calls or Go To Meeting calls that last for a couple of hours.
I'd love to know how others, who find themselves regularly the same situation as our company, utilize Tempo?
Is there a different time tracker that we could use? We do love the integration with Jira Cloud (that's something Toggl doesn't provide).
Ahhh, I see! Thanks so much for the help and informative reply @Nic Brough -Adaptavist-, I really appreciate it! We'll look into using internal issues. Thanks for the link!