What syncs
| ClockLap | Sent as | Notes |
|---|---|---|
| Jira project | ClockLap project | An existing one, or a new one with the project key as its code |
| Issue | Task “PRJ-12 Summary” | Estimate and assignee (by email) come too; done issues finish the task |
| Time on the task | Worklog | Start, duration and the person’s name; updated or removed when the time changes |
Worklogs are sent once per time entry. Each one carries a marker, so a retry after a lost answer finds the worklog it already made instead of logging the time twice.
How it works
- ConnectSign in with Atlassian, or paste your site, email and an API token.
- Map projectsPick the ClockLap project for each Jira project you want, or make a new one.
- Issues come inHourly, daily or when you press Import: open issues, or all, optionally narrowed with JQL.
- Time goes backSwitch on worklogs: as soon as the time ends, or once it is approved.
People
Assignees are matched by email when Jira shares it. Worklogs are written by the connected account, with the person who worked in the comment.
What you need
- Jira Cloud
- An account that can browse the projects and log work
Every run keeps a history: who and what was sent, per-line results, plain-language errors with a fix, and a redacted request log for admins. Webhooks fire on task.created, task.updated, time_entry.clocked_out.
Questions
Does it work with Jira Data Center?
Not yet: the connection uses the Jira Cloud REST API.
Who is the worklog author?
The connected Jira account, since Jira doesn’t let apps log work on someone else’s behalf. The person’s name is in the comment.
Is the Jira connection included in the price?
Yes. Every connection is part of every ClockLap plan: $1 per staff member and $2 per manager or admin a month, with no add-ons.
Is ClockLap affiliated with Jira?
No. ClockLap connects to Jira using its published API; it isn’t affiliated with or endorsed by Jira. The connection is in beta while we verify it with live accounts.