I am wondering what is the recommended approach to log non-billable hours such as various interruptions, meetings, unexpected support tasks and what not? The goal is to have employees log all "worked hours" in a week but on the other hand, they do not always fit into JIRA project issues.
Personally we have separate internal projects for non-billable activities. Also you may create non-billable task in your current project or introduce "Non billable" issue type.
Non-billable projects, issues or issue-types can be easily excluded when viewing reporting or generating time-sheets. You can use Projects control or create appropriate filter and add it to favorites.
We created internal projects and a special "billing type field" for all customer projects. We can have both billable and non billable issues for the customer projects. However, still sometimes we would like to log less billable hours to the customer project issues. System performance can be bad or our employee could be inexperienced for the project and it can take longer than expected. I think it would be nice if we can log both billable and non-billable hours under the same issue because we would like to follow both actual time spent and time to be billed for the issue.
I will apreciate if you have any ideas. Thanks.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs