ObraLedger

Type to search.

Worklogs

Jira

Projects, tasks and the hours logged against them, brought in from Jira so timesheets and invoices start from work already recorded.

Your team already logs time in Jira. Connect it and those hours become timesheets here, against the right project and task, ready to approve and invoice without anyone retyping them.

What you can do

  • Bring in projects, from Jira projects or from epics, whichever matches how you organize work.
  • Bring in issues as tasks: bugs, stories, tasks, sub-tasks and the rest.
  • Turn worklogs into timesheets, for the issue types you choose.
  • Bring across the people and teams, and the attachments on issues.
  • Keep it current as things change in Jira.

How it works in practice

Connect with an API token. Create one in your Jira account’s security settings, then enter your Jira address, user name and token in the Jira card under Settings → Extensions. Test the connection before you sync.

Match your structure. Say whether a customer here is a Jira project or a Jira customer, and whether a project is a Jira project or an epic. Then pick which issue types carry billable time.

Choose how far back to start. The first import goes back six months unless you set another date.

Changes follow on their own. Add the webhook in Jira’s admin settings and created, changed or deleted issues, worklogs, projects and users come across as they happen.

Good to know

  • It’s one way. Work comes in from Jira; nothing is written back.
  • Approval still happens here. See projects and timesheets.
  • Check your plan first. Jira can need a license of its own; the extensions page shows a badge where your plan doesn’t cover it.

Other extensions

Something here wrong or missing? Tell us - the guide is maintained alongside the product.

See it with your own numbers.

Everything the guide describes, unlocked for a month. No card.