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.
We work with clients who buy hours in "buckets". For example, they'll buy 1000hrs here or 500hrs there. The issue we're having is determining the best way to allocate tasks to those specific buckets of hours. There's 2 current thought processes we have at the company of how to proceed..
1) Create an issue/story named "Client X : 100hrs" then assign all tasks to that individual story
2) Create a project named "Client" then have each epic be that buck of hours "100hrs" "500hrs" etc. then have task assigned to that specific epic.
End goal: See the number of hours a client has allocated, see how many hours have been billed (and those specific tasks), and see how many billable hours they have left.
Thanks in advance for any suggestions!
Do you have the planner and cost tracker modules for Tempo?
These are the features designed to track actual vs planned work.
Re how to log work, I would suggest you use accounts for each bucket, associate the accounts with the required projects.
This is how it worked at my last site, although my involvement was limited to installing and configuration advice.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.