LogQuillWorking hours
The countries you operate in, the hours expected on each day of the week, the day weeks start on, and the language of LogQuill's emails.
Who: people with General settings. Open Admin, then General.
Countries you operate in
The countries your company works from: usually one, sometimes two or three. They're the only countries that holiday lists, teams, people and leave plans can be given, so nobody has to scroll through every country in the world.
The first is the default for everything: everyone whose team or own setting doesn't say otherwise takes its public holidays and its leave plans. Make default moves another one to the top. With a single country, LogQuill hides the country pickers everywhere else: everyone is there.
A new site starts with the country of its Jira site's time zone (Jira doesn't say a country itself), and the setup checklist asks you to check it.
Removing a country that something uses says what moves before you save:
- teams based there move to the default country;
- people given it as their own country go back to their teams' country or the default;
- leave plans set for it end, so its people follow the default country's.
Its holiday lists are kept, unused, so adding the country back finds them.
Screenshot to add: public/screenshots/admin/countries.png
Countries you operate in on Admin, General: two countries, the first marked Default.
Admin → General. With two countries added (for example Morocco and France), capture the Countries you operate in section: the list with the Default badge, the usage under each country and Make default on the second.
Goal hours per day
How many hours are expected on each day of the week. Set a day to 0 if it isn't worked: it's shaded as time off across the app.
These hours drive:
- each timesheet's required time (public holidays count as zero);
- the daily limit, when your site limits a day's time to its working hours (Time logging);
- people's targets on the week board and the dashboard;
- what a day (
1d) means when someone plans a total in days: the most common day's hours.
Screenshot to add: public/screenshots/admin/working-hours.png
The goal hours per day, with Jira's own working time shown for comparison.
Admin → General. Capture the Goal hours per day section with the seven days and the note comparing them with Jira's time tracking settings.
Week starts on
The first day of the week across the app: how the week board and the timesheet table cut weeks, and which week This week is.
Email language
The language of every email LogQuill sends for the site, English or Français: missing-time reminders, timesheet and absence emails, shared reports, and notices to admins. HR's page for approving an absence from its email follows it too.
It's one language for the whole site, not each person's own: an email goes to several people at once (the person, their leaders, HR), and they all read the same one. The app itself still follows each person's own language in Personal settings. To see what an email looks like, send one from Admin → Timesheets → Test the emails.
Jira's own working time
Jira shows time on issues (estimates, "1d") with its own working day and week, set in Jira's time tracking settings. LogQuill compares them with the hours above and says whether they match. Keep them the same, so issues read the same in Jira as in LogQuill; the notice links to Jira's settings.
Jira's time tracking provider
If LogQuill isn't Jira's time tracking provider yet, a notice says so here. Until it is, people can log time with Jira's own Log work button: the Jira sync still brings that time into LogQuill, but it skips LogQuill's rules (locked timesheets, daily limits, required fields). See Install to change it.