Jira — link a project and track time

Link a docket project to a Jira project, choose where time lives, and change your mind safely.

Once the connection is set up, a project manager links each docket project to its Jira counterpart.

Linking the project

Open the project, go to Settings, and find the Jira panel.
Choose the connection (the Jira site).
Search for the Jira project you want to mirror and select it.
Click Link project.

docket now imports the project's issues in the background (this can take a moment for large projects). When it's done:

The Tickets tab shows the Jira issues (read-only, with their Jira key).
Boards and Roadmap tabs disappear — that planning lives in Jira now.

Time-sync settings (choose where time lives)

When you link a project — and any time afterwards under Project → Settings → Jira — you control these switches:

Push time booked in docket to Jira (on by default). This is the setting that decides whether time also lands in Jira. Turn it off and the time you track in docket on these tickets stays in docket only — nothing is written to the Jira worklog. Turn it on and every booking is pushed to the matching Jira issue (as the person who booked it).
Import time logged directly in Jira (on by default) — pulls worklogs that were entered in Jira into docket, read-only, so they show up in docket's reports.
Turn imported time into real docket time entries (off by default, only visible while the import switch is on) — for team members whose Jira account is mapped to a docket user and who have a service set, newly imported Jira worklogs become real docket time entries: they count in reports and revenue exactly as if they had been booked in docket, rated at the user's service and rounded to 15-minute steps. Time of unmapped people stays read-only. After conversion, docket is the source of truth — edit or delete the entry in docket, not in Jira (a deletion in Jira removes the converted entry in docket, but edits in Jira are ignored). The switch only affects time imported after you enable it.

So yes: you can absolutely track time in docket on Jira tickets without it appearing in Jira — just leave "Push time booked in docket to Jira" switched off.

Changing the settings later

You can flip either switch at any time under Project → Settings → Jira. What happens:

Turning push OFF: future bookings stop syncing to Jira. Time you already pushed stays in Jira — switching off does not retroactively delete it (use "Remove docket time from Jira" for that, below).
Turning push ON: new bookings sync automatically from then on. To also send past docket entries that were never pushed, click "Sync existing docket time to Jira now" — this is a full catch-up that pushes every docket entry on this project that isn't in Jira yet.
"Remove docket time from Jira" (admins only): deletes every worklog docket pushed to Jira for this project. Your docket time entries are untouched — only the copies in Jira are removed. Use this if you decide the time shouldn't be in Jira after all.
- Core-Jira note: docket can only delete a worklog as its original author, so entries from people who no longer have a connected Jira token can't be removed automatically and are flagged instead. (On Tempo this limitation doesn't apply — removal works for everyone via the connection's Tempo token.)

Tempo behaves the same as core Jira for all of the above (push, catch-up sync, and removal).

Everyday use

Find a Jira ticket: open the project's Tickets tab, or pick it in the time-tracking ticket selector (search by its Jira key).
Book time: track time exactly as you do on any docket ticket.
Check the sync: each time entry on a Jira ticket shows a small badge —
- Synced to Jira ✓ — pushed successfully.
- Syncing… — in progress.
- Jira sync failed — click Retry (see troubleshooting).
- Not in Jira — connect your token — you haven't added your token yet; do Part 2 of the setup, then Retry.
Open in Jira: click the Jira key badge on any mirrored ticket to jump to the issue.

Assignments, statuses, due dates and priorities always come from Jira — change them in Jira and they update in docket on the next sync (a few minutes). You can't edit a mirrored ticket in docket; you can only book time on it.

Switching a project to Jira after you've already tracked time

Very common: a project runs for a while as a normal docket project — you've created tickets and booked time on them — and then you decide to link it to Jira. Nothing is lost, and nothing is overwritten. Here's exactly what happens:

Your existing docket tickets and all their tracked time stay. Linking only adds the imported Jira issues as new tickets; it never touches or deletes your original docket tickets.
The project then holds both: your old docket tickets and the imported Jira tickets, side by side. New work is tracked on the Jira tickets.
Because the Tickets tab now opens Jira, you won't browse the old docket tickets in that tab anymore. But they're still fully in the project: their time keeps counting in the budget, Controlling and reports, and you can still select them by name/number in the time-tracking view to view or edit those entries.
The time you booked on the old docket tickets is not sent to Jira — those tickets have no Jira counterpart, so there's nothing to push them to. Only time on the imported Jira tickets syncs. (The "Sync existing docket time to Jira" button also only covers the Jira tickets.)
Changed your mind? Unlink the project (Project → Settings → Jira → Unlink): the Tickets, Boards and Roadmap tabs come back. Mirrored Jira tickets with booked time stay (with all time intact); mirrored tickets you never booked anything on are removed again — they only existed because of the link.

In short: switching mid-project is safe. Your history stays in docket for reporting; from the switch onward, new time is tracked against Jira tickets.

Linked the wrong Jira project — or switching to a different one

There is no "change project" button on purpose: you unlink and then link the right project. docket is built so that this is safe in both directions:

If you notice right away (no time booked yet): just unlink. All the imported tickets are empty, so they're removed again automatically — the project is exactly as it was before, and you can link the correct Jira project immediately.

If time was already booked on the wrong project's tickets: unlink and link the right project. Then:

Tickets with booked time stay in docket — hours, budget and Controlling don't change. They're closed by the daily check (so they leave the Workload view) and become frozen history.
New time booked on those old tickets stays in docket only — it's never pushed to the previously linked Jira project.
Time you want on the new project's tickets: move it. Go to Timetracking → Reports, select the entries, and use Move to change their project and ticket. The Jira side follows automatically: the worklog is removed from the old Jira issue and — if push is on — created on the new one.
Worklogs docket already pushed to the wrong Jira project don't disappear on their own. If they shouldn't stay there, click "Remove docket time from Jira" before you unlink — after unlinking, docket can no longer clean up that Jira project.

Tickets "stuck" in another project: if the Jira project you link is already mirrored in a different docket project with booked time (for example after moving a Jira integration from one docket project to another), docket shows a warning — both when you pick the project and afterwards in the settings panel. Those tickets are never moved automatically, because their hours and revenue would silently switch projects. Move their time entries via Timetracking → Reports → Move (or leave them where they are); tickets without any remaining time then move to the newly linked project automatically within a day.

Next: how the sync behaves, and what to do when it looks wrong.