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.
Hi,
i was wondering, what are solutions in your companies to log work done in the meantime of other issue.
For example - i have to reinstall windows - it lasts about 3 hours , but one hour is almost free - i just need to click "OK" from time to time. So i've done 3 other issues during installation process (1 hour).
Sum of work logged is 4 hours, but in reality it was 3 hours.
In that case multitasking is great solution, but effect is that in 8-hour workday i have much more hours of work logged.
How to make any KPI with these?
-at least 5 hour per day logged?
-stop checking worklogs and focus on SLA?
What are best practices?
I can use this solution in other project but in that case it generates false data. Let's take my example with windows reinstall. With start-stop it will take 0,5 hour of my work to reinstall but whole process takes 3 hours.
I'm looking for solution to not bend the reality - reinstall takes 3 hours, but to find a good KPI in that case.
I hope you get my point.
Cheers, Ewa