For now I’d like to stick to the subject of timesheets/timetracking. SLA is a complete different story for me right now.
Here is some information on how we track time right now:
- We have stoped using iTop for our issue-tracking. We now do all that which ERPNexts built in Support-modul and it’s Issues.
- We added Issue as a custom field to our timescheet detail as the smaller version of Task. The top down order for us is now Project, Task and Issue. As Issue* is also displayed in the DASHBOARD of Projects when referenced in the contact-section in the Issue I recommend taking this into the core-version as it is very interesting to see how much time is spent on solving Issues. Especially for companies providing billable services on call.
- We added a "kilometer driven** custom field in our timesheet detail for reference. This we still need to solve in a better way (maybe as kind of Stock Entry (not that important right now)).
- We use the field ‘Note’ in Timesheet for customer reference text on the work we have done for them. This we would like to have linked to Sales Invoice. (This I have adressed in antoher topic though)
For now we create invoices toward our customers in ERPNext only in theory. A collegue then makes a manual invoice via LibreOffice and copies the invoice-no and items.
It is still a little unclear to me when to use several rows in the timesheet. For now we just do one per timesheet.
As a little reminder for people who are new to ERPNext: All timesheets with the “Bill-Box” ticked will be drawn to an invoice when referencing the according project.