Connect
Connect your Jira Cloud site with a service account that only reads. If you work with Tempo Timesheets, add the Tempo token.
Jira · Time tracking · Tempo
Time tracking for Jira that goes all the way to the invoice.
Your team keeps planning and working in Jira. In docket you book the time on the Jira tickets, it lands in Jira as a worklog and at the same time in the client's budget, the client report and on the invoice. Or you keep booking in Jira or Tempo, and docket picks the hours up.
No card, no sales call. For Jira Cloud. The integration is included in the price.
Jira for the work. docket for the hours and the money.
Jira ↔ docket
Booked on the Jira ticket. Counted everywhere.
You link a docket project with its Jira project, and docket mirrors the issues, read-only, with their Jira key. You book time on them like on any ticket: by hand, with the stopwatch or in your own words with AI. The time goes to Jira as a worklog under your own name and counts in docket right away, in the budget, in controlling and on the next invoice.
- New and changed issues arrive after a few minutes
- Find Jira tickets in time tracking by their key, like
QAM-142 - Every time entry is exactly one worklog: nothing is sent twice
- Whether time flows back to Jira is your choice, per project
Jira
QAM-142Relaunch: navigation
docket
QAM-142Relaunch: navigation
Set up in three steps.
Jira stays as it is. docket reads your projects with a token that can only read, and writes nothing but your team's worklogs.
Link
Link the docket project with its Jira project, all of it or just some epics. docket fetches the issues in the background.
Book
Book time on the Jira tickets. Each person connects their Atlassian account once, so the time shows in Jira under their name.
What agencies with Jira really need.
Any plugin can track time. It gets interesting once client projects, freelancers and budgets come in.
01
Keep booking in Jira or Tempo? Fine.
Worklogs logged straight in Jira or Tempo are fetched every few minutes and shown in the project's controlling. If you like, they become real docket time entries, valued at the person's service, and count in budgets, reports and invoices.
Margin noteYou don't have to change your team's habits. You can, if you want to.
02
Freelancers and partner agencies without a docket account.
When someone without a docket account books in Jira, docket creates a placeholder. Their time counts in the budget, at the rate you give them. Placeholders can't sign in and take no seat. Once the person gets an account, you merge the two.
Margin noteDifferent rates for a freelancer and a partner agency? One service per placeholder.
03
One Jira project, several client projects.
If several of your projects live as epics in one Jira project, you link each docket project with its epics only, stories, tasks and sub-tasks included. Every epic belongs to exactly one project, and so to one budget.
Margin noteYou can change the cut later. Time booked stays where it is.
04
Part of the team has no Jira?
Then Jira adds to the project instead of replacing it: docket's own tickets, boards and roadmap stay, the Jira issues sit below them. Some book on Jira tickets, others on docket tickets, all in one budget.
Margin noteProject work without a Jira licence for everyone. For an agency that adds up quickly.
05
Planning stays in Jira.
Status, assignees, due dates and priorities come from Jira and aren't edited in docket. The workload still shows how many Jira tickets are with whom.
Margin noteOne truth for the work, one for the hours. Not two ticket systems.
06
Switch over without losing anything.
Link a project that already has tickets and time, and the Jira issues only come in addition. Unlink it, and tickets with booked time stay. What docket already sent to Jira, an admin can have removed there if they wish.
Margin notePicked the wrong Jira project? Unlink, link the right one. docket clears away the empty tickets.
Quick questions, quick answers.
Do we need Tempo?
No. docket writes the time straight into the Jira issue's worklog. If you already use Tempo Timesheets, docket books through Tempo and takes over its worklogs too. Time tracking, budgets, client reports and invoices are part of docket anyway.
Does it work with Jira Server or Data Center?
No, only with Jira Cloud, a site at atlassian.net.
What does docket write into our Jira?
Only worklogs, the time your team books in docket, and only in projects where you switched that on. Tickets, statuses and comments stay untouched. The service account docket reads your projects with only needs read access.
Is time counted twice if we book in docket and in Jira?
No. Every time entry from docket is tied to exactly one worklog, and what docket sends to Jira it doesn't fetch back as someone else's time. Time logged only in Jira counts in budgets and invoices once you have it turned into docket time entries.
What does the Jira integration cost?
Nothing extra, it's included. You pay per person by role: someone who only books time on their projects is a timetracker at €5 a month. Placeholders for freelancers without an account cost nothing. All prices on the pricing page.
How fast do changes from Jira arrive?
docket fetches new and changed issues and time logged in Jira about every five minutes. Time you book in docket goes to Jira right after saving.
Your team stays in Jira. The hours arrive.
Try it free for 14 daysNo card. All the details: the Jira integration in the help. Questions first? info@docket.rocks.
