LogQuill

Jira sync

How LogQuill keeps its people and worklogs in step with Jira, and what to do when it isn't.

Who: people with Manage the Jira sync. Open Admin, then Jira sync.

Jira is the reference, and LogQuill follows it.

How it works

  • Live updates: when a worklog or a person is added, edited or deleted in Jira, LogQuill applies it within minutes. Plans aren't in Jira's work log, so they live in LogQuill only.
  • Daily check: once a day, LogQuill reads what changed in Jira since the last sync, to catch any live update that went missing.
  • Time changed in Jira inside a submitted or approved timesheet is applied too, and the timesheet is flagged for its reviewers.
  • People deactivated or deleted in Jira are marked as such: a Deactivated or Deleted badge next to their name everywhere, and "(Deactivated)" after it in exports. They keep their history and teams, but nothing is expected of them and LogQuill stops acting for them:
    • no reminders or other emails, and no holiday country to pick;
    • an absence approval chain skips them, and a team that named only people who left goes back to its active leaders;
    • their connected calendar is no longer read or written;
    • they don't count as an admin, so the site is offered someone to take over if no admin is left.
  • LogQuill's own rules (locks, daily limits, required fields) don't apply to changes made directly in Jira. The audit log records them as made in Jira.

Is it in step?

The page says whether LogQuill is in step with Jira, is Syncing with Jira, or may be out of step, with the reason. When it may be out of step, a notice shows at the top of the admin area, and a dot on Admin in the sidebar.

Screenshot to add: public/screenshots/admin/jira-sync.png

The Jira sync tab, in step, with the recent runs listed.

Admin → Jira sync. Capture the health line, Check for changes and Sync now, the recent runs, and the "How it works" part.

Running a sync yourself

  • Check for changes: quick. Updates everyone's name, avatar, email and account status, and reads only the worklogs changed or deleted since the last sync.
  • Sync now: slow. Updates everyone and reads every worklog in Jira, all the way back. Use it when older time looks wrong. It uses a lot of your site's Jira allowance.

Recent runs are listed with what each one found.

Worklogs made by apps

Some apps (Tempo, for example) save worklogs in Jira under their own app account rather than the person's. LogQuill can't tell whose time those are, so they aren't counted in anyone's timesheet. This page shows how many each app made. For Tempo, LogQuill can find the real authors: Import from Tempo.

Right after installing

The first sync, bringing in your people and past worklogs, starts on its own when the app is installed. If it fails, LogQuill tries again within the hour, and you can restart it from here.