Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,300,290
Community Members
 
Community Events
165
Community Groups

Why is it that all of my accounts are showing up as billable hours in the Tempo logged time report?

I created a number of accounts that are tied to account categories that should allow for billable (Capitalized, Billable) and non billable (Internal, Operational) logging of time. When I enter time under these accounts that are tied to the account categories, all hours appear as billable hours within the tempo time report. Any ideas on what is happening? image.pngimage.pngimage.pngimage.png

2 answers

Tempo has setup all worked hours as billable by default. For those who only use Billable/non-Billable Accounts at the issue level, this "B" column in the report is not meant for you to use. This is part of the "Set Billable hours" feature for those who actually need to manage billable hours at the worklog level. So when you run Tempo Logged Time reports with Billable Accounts, you only need to show the logged hours. Even if you decided to show this "B" column, it would be the same as logged hours.

As for internal issues, they are the only issues that will have no billable hours by default.

On Cloud, Set billable hours is a project setting. On Server/DC, it's a global setting. For those who use both features, you will have to maintain manually the billable hours on all the worklogs with bulk action on Cloud, or edit each worklog one by one on Server/DC (bulk action is coming soon). 

You can check out our Best practices for tracking billable hours. https://help.tempo.io/cloud/en/tempo-timesheets/organizing-data-using-tempo-accounts/best-practices-for-tracking-billable-hours.html


Also, we have YouTube videos on Billable hours: https://youtu.be/a6BjQ59i70E and on Billable Accounts https://youtu.be/OHfmhnE5714.

Hope this answered your question.

Susan Wu
Tempo Product Expert

I have the same issue I'm trying to solve!  Any help out there?

Hi, I had the same issue. I think it must be a bug in Tempo...but I solved it by using these functionality - https://help.tempo.io/cloud/en/tempo-timesheets/setting-up-and-configuring-tempo-timesheets/creating-and-configuring-internal-issues.html

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you