LogQuillFirst setup
The settings to look at before your teams start logging time, in the order that makes sense.
Who: a LogQuill administrator. Every setting lives under Admin in the sidebar, and can be changed later. Nothing here is required before people start logging time, but timesheets and reminders only make sense once the first few are set.
The setup checklist
Until the site is set up, the Dashboard shows a Set up LogQuill card to admins, with a dot on Dashboard in the sidebar saying how many steps are left. It lists the countries you operate in, working hours, public holidays, timesheets, teams and Jira's time tracking, and each step shows how far along the site is:
- Countries you operate in starts with the country of your Jira site's time zone. It's done once you save the list, or choose Mark as done if that country is right.
- Working hours and Timesheets come with defaults. They count as done once you save their tab, or choose Mark as done if the defaults are right.
- Public holidays is done once the default country has holidays, Teams once there is a team, and Jira's time tracking once LogQuill is Jira's time tracking provider.
- Set up opens the page where the step is done. Mark as done also fits a step your site does without.
You only see the steps you can do: someone who can only open Admin → Holidays sees that one. Hide for now hides it from your own dashboard. Setup checklist at the top of the dashboard brings it back. Mark all as done marks every step done and removes the checklist for good; each setting stays in Admin. Marking steps done is in the audit log.
Screenshot to add: public/screenshots/getting-started/setup-checklist.png
The setup checklist on the dashboard, with two of six steps done.
On a new site, sign in as the admin, save the countries you operate in and the working hours. Open the Dashboard and capture the Set up LogQuill card with two steps done and four to go.
The steps below go through each setting in more detail.
Countries you operate in
Admin → General. The countries your company works from; the first is the default for holidays, teams, people and leave plans. Every country picker offers only these. Countries you operate in
Working hours and the start of the week
Admin → General. How many hours are expected on each day of the week, and the day weeks start on. Required time on timesheets, the daily limit and the dashboard all come from these. Working hours
Public holidays
Admin → Holidays. A holiday list for each country you operate in, and which country applies to whom. Holidays count as days off. Holidays
Roles
Admin → People & roles. Everyone starts as a Member. Give Manager to those who run teams and timesheets for the whole organization, HR to those who approve absences, and Admin to those who set things up. Adjust what each role allows, or add your own. People and roles
Teams
Teams in the sidebar. Create your teams, choose who leads each one, and add their members. Timesheets are handed in to a team, and its leader reviews them, so everyone who tracks time should be in a team. Teams
Timesheets
Admin → Timesheets. How long a timesheet covers (one to four weeks), whether incomplete ones can be handed in, what people can still change once they have, and the reminder emails. Timesheet settings
What people fill in
Admin → Time logging. Work types, extra worklog fields, and whether a day's logged or planned time may go past its working hours. Time logging
Accounts (if you bill or track time by customer)
Admin → Accounts. Who the time is worked for, and which projects and issues send their time to each account. Accounts
Coming from Tempo?
Admin → Jira sync. Bring Tempo's worklogs, accounts and attributes into LogQuill. Import from Tempo
Emails
LogQuill emails people about their timesheets (missing time, hand-ins, approvals, sends back), their absences (to approvers when it's their turn, to HR, and to the person once decided) and reports shared with them; administrators about the subscription and the audit log's clear-out. They're all in the site's email language, English or French, set in Admin → General. It can only email people whose email address Jira shares with apps. Someone who hides it can change that in their Atlassian profile; see Personal settings.