Jira timesheets your team leaders can approve
People log time on Jira issues as they do today. At the end of each period they hand in a timesheet, their team leader approves it or sends it back with a reason, and the approved period locks. Every worklog stays a Jira worklog.
30-day free trial through the Atlassian Marketplace. Jira Cloud. English and French.
From the first worklog to an approved period
- 1
Log time on issues
From Log work on the issue, the Time Tracking page, a timer, or suggestions from your Jira activity and calendar. Each entry is saved on the Jira issue, as the person.
- 2
Check the period
Required, logged and missing hours, day by day and by project. Weekends, public holidays and approved absences need nothing.
- 3
Hand it in
Once the period has ended, to a team the person is a member of, with a note for the reviewer if they like.
- 4
Approve or send back
The team leader approves, with a comment, or sends it back with a reason the person sees. Approved, the period is locked.
Made for the people who approve
A team leader sees what waits for them, decides in one dialog, and hears about anything that changes afterwards.
What's waiting, oldest first
A dashboard widget and the team's Approvals tab list the timesheets handed in. The period view shows where every member stands, and why someone can't hand theirs in yet.
One dialog to decide
The person's time day by day against what was required, their note, then Approve or Reject. Reopen an approved one, or hand one in for someone who can't.
Changes in Jira are flagged
If a worklog in a submitted or approved timesheet is changed directly in Jira, LogQuill applies it and flags the timesheet with what changed.
An approval log
Every timesheet handed in, approved or sent back, with the reasons and notes, filtered by action or period.
Locks that say why
Locked days show a padlock in the table and on the board. Hover it to see why, and what's still allowed.
Nobody approves their own
A leader's timesheet goes to someone above them, unless your site lets leaders review their own.
Set once by an admin, applied everywhere
Periods of one to four weeks
Starting on the weekday you choose. A later change applies from a date onward, and timesheets already handed in keep theirs.
What counts as complete
Refuse incomplete timesheets or accept them, with a tolerance over the whole period. Choose whether extra hours on one day make up for a short one.
What stays editable
After handing in, allow or block logging, editing and deleting, separately for logged time and plans. Approved is always locked.
Missing time emails
Before a period ends, after, or both. Copy team leaders and up to 20 other addresses, such as HR or a shared inbox.
Status emails
When a timesheet is handed in, approved, sent back or reopened, each with its own switch.
Required hours that follow life
Public holidays by country and approved absences lower what a period needs. A handed-in timesheet keeps its numbers.
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.