Fillchecker offers easy-understand Timesheet reports showing individual users' or groups' worklog completion based on time models depending on the expected daily working hours e.g. part-time and full-time employees. If there is anything out of the ordinary (currently if the worklog durations don’t reach the required minimum, but other features are coming), it will then send pre-set notifications to the user and the relevant managers. As such, it offers easier compliance compatibility to Jira’s time tracking feature.
Due to this, it is a perfect complimentary app to EverIT’s own Timetracker for Jira plugin - or any other time tracking tool that uses Jira’s native database for storing worklog data. We’ve prepared use cases to show you examples on how they can work together, and how they can bring about conversations on proper time tracking methods inside an organization.
Use Case 1.
Finding missing worklogs before invoicing
project is close to deadline - fillchecker alerts scrum master of missing worklogs - guilty colleague has no time at the moment to create worklogs, busy with deadline stuff - scrum master can fill the colleague’s timesheet with timetracker’s log work on behalf of other user feature
Use Case 2.
Investigating overtime
If set up for daily alerts, Fillchecker’s email notifications are the first line of defense that can bring Management’s attention to a project consuming too much energy, especially if it starts to become a trend after a few days. On one hand, it can trigger conversations about the amount of resource allocated to the given project. On the other, it can serve as a basis for talks about different compensation levels.
gif about a fillchecker timesheet report showing mostly too much time logged for members
In the second case, it will be beneficial to differentiate the work that was done during a team member’s normal working hours, and what had to be done in overtime to finish the tasks at hand. Third-party time-tracking tools, our Timetracker included, offer the ability to add extra details to worklogs, in this example, in the form of a custom tag called Overtime. Seeing an employee with a pattern of doing too much work without proper explanation on the why can also bring up talks on proper use of tags for worklogs. For more information on that, we have prepared 10 use cases featuring custom tags and billing info.(link)
gif about seeing an employee with 10 hours logged for a day - switching to timetracker - checking that employee’s calendar - or report?