Leave management that lives in Jira
People ask for time off where they already log their time. Each team's approvers decide, HR follows from their inbox without a Jira account, balances are worked out live, and timesheets already know who was away.
30-day free trial through the Atlassian Marketplace. Jira Cloud. English and French.
From a request to payroll
- 1
Ask for time off
Pick a type, the days (half days at either end), add a note, and attach a document if the type asks for one. The balance after the request is shown before sending.
- 2
The team approves
Through the team's approval chain: its leader, named people one after the other, or any one of them. Set once per kind of team.
- 3
HR approves, if the type asks
In LogQuill, or from one email with a link that opens the request and its documents. No Jira licence needed.
- 4
Everything follows
Required hours drop on timesheets, the absence shows on the team calendar, and it can go to Google Calendar or Outlook as Out of office.
Allowances that work themselves out
A balance is never stored or topped up on a schedule. It is worked out each time from the plan's rules, the person's start date and their absences, so a change to a plan shows everywhere at once.
Allowance plans
Days a year, given at the start of the year or a twelfth each month. A leave year that starts in any month. More days after a number of months' service.
Carry-over
Up to a number of days carried into the next year, and lost after a few months if you want. Each person sees what carries over and when.
By type, country and person
One plan for everyone, another for one country you operate in, and a plan of their own for the odd person. Changes can start on a future date.
Too few days left
Per absence type, refuse a request that goes below zero, or let it through with a warning. Approvers see the balance before and after.
HR adjusts and imports
Correct a balance with a reason, import opening balances or start dates from a file, and export everyone's balances.
An absence report for payroll
Days off per person and type, by day, week, month or year, exported to Excel or CSV.
Absence types that fit your policy
Approval chains per team
A default chain, one per team type, or a team's own. Nobody approves their own absence, and a deactivated approver is skipped.
HR without a Jira account
Up to ten HR addresses get each request with a link that works once and for two weeks. The first to decide settles it.
Supporting documents
Per type: not asked, optional, or required before approval, such as a medical certificate. Stored encrypted, opened only by the person, HR and whoever decides.
What a day off allows
Per type: logging time with a warning, no logging at all, or worklogs counted as overtime. Public holidays come per country.
Odoo and calendars
Time off kept in Odoo shows in LogQuill, read every hour. Out of office events in Google Calendar or Outlook can become absences.
See who's away
A month calendar for the site or one team, On leave badges next to names, and a Who's out this week widget.
Also in LogQuill
- Jira timesheetsPeriods handed in to team leaders, approved or sent back, then locked. Required hours follow absences.
- Switching from TempoImport Tempo's worklogs under the people who logged them, with accounts, work attributes and teams.
Odoo is a trademark of its owner. Google Calendar and Outlook are trademarks of Google and Microsoft.
Give your team a timesheet they will actually fill in
Install from the Atlassian Marketplace, set it up in an afternoon, and try it free for 30 days next to whatever you use today.
Rather see it first? Book a 30-minute demo.