It would be great if we could set different options for the Timesheet period instead of a week like it is now. For example, monthly timesheets or semi-monthly timesheets instead.
We are a professional services company and we invoice our clients and do payroll on a semi-monthly basis. Our pay periods are the 1st-15th and then 16th-end of month. We need to lock time entries for these periods before we do invoicing to ensure we have all project time entered.
The problem we are having with Timesheets being a calendar week is that the 15th and end of month will usually fall in the middle of the week. We can submit and approve time in the middle of the week but that will either lock the week which won't allow time entries for the remaining days or it won't lock the week and resources can then add time to days that were already approved which would get missed at invoicing.
-
Hello Mike!
Thanks for your feedback.
I've created it in the backlog (internal id 31556). Unfortunately, it is currently not in our roadmap, but we will keep it in mind, as we are sorting backlog items based on user votes and feature complexity.
I'll discuss it with our product owners and will post updates here if we will start working on it.Regards,
Maxim -
This would be incredibly helpful for us as well. We use a semi-monthly time reporting period. This means we have to send in time for the 1st to the 15th and the 16th to the end of month. Currently we have to simply instruct users to not put time into closed periods, this would be helpful to line up to other period types, or perhaps to iterations in DevOps. We could just setup our iterations that way.
Please sign in to leave a comment.
Comments
2 comments