Jira integration — overview
What the Jira integration does, who has to do what, and where to go next.
Link a Jira Cloud project to a docket project and you can see your Jira tickets in docket and book time on them — while your hours also flow back into Jira.
In short: an admin connects your Jira site once and links each project. Every team member connects their personal Jira token once. After that, Jira tickets appear under the project's Tickets tab and you track time on them just like any other ticket.
What you get
- Jira issues appear in docket as read-only tickets (with their Jira key, e.g.
ABC-123, and a one-click link back to Jira). - You book time on those tickets in docket — and it's pushed to the Jira issue's worklog under your name.
- Time already logged in Jira is visible in docket's reports.
- The Workload overview shows how many Jira tickets are assigned to each person.
- For a linked project, planning stays in Jira: docket's Boards and Roadmap tabs are hidden, and the Tickets tab shows the Jira issues.
You decide per project whether time flows to Jira at all — tracking Jira tickets in docket without writing anything back is a supported setup. See time-sync settings.
Who does what
| Step | Who | Where |
|---|---|---|
| Create the service-account token and connect the Jira site | Admin, once | Set up the connection |
| Add a personal Jira token | Every team member, once | Set up the connection |
| Link a docket project to a Jira project | Project manager, per project | Link a project |
| Book time on Jira tickets | Everyone, daily | Link a project |
Before you start
- A Jira Cloud site (e.g.
https://yourcompany.atlassian.net). - A service account in Jira with permission to browse the projects you want to link (a dedicated "bot" account is recommended). You'll need its email and an API token.
- Each team member's own Atlassian API token — so their time is logged in Jira as them.
- In docket: admin rights to create the connection; project manager rights to link a project.
Where to go next
- Set up the connection — API tokens, connecting your Jira site, and each team member's personal token.
- Link a project and track time — linking, the time-sync switches, changing your mind, and everyday use.
- Sync behaviour & troubleshooting — how often docket syncs, how double-bookings are prevented, how issue types and statuses are handled, and what to do when something looks wrong.