layercell
How we build Documentation Support Contact

Documentation

Log Jira time entries reliably without losing them

Jira Cloud teams cannot log time reliably: batched worklog writes fail under API rate limits, partial failures silently drop entries, and existing marketplace trackers leave timesheets incomplete. They need a way to record hours that never loses an entry and exports from Jira's own data.

Overview

Log and track work hours against Jira issues from one page in Jira's Apps menu, without losing work logs.

Key Features

  • Start and stop a timer that keeps running when you leave the page and come back, then save the elapsed time as a worklog.
  • Enter several worklogs at once in a batch grid. Each row is checked on its own, so one invalid row does not block the others.
  • If Jira is busy or unreachable, entries are kept in a retry queue and sent again. The app checks Jira first, so an entry is not logged twice.
  • Export the worklogs for a user and a date range to CSV, as Jira records them. Ranges can span up to 366 days.
  • Anything the app stores is deleted within 30 days.

Getting Started

Install from the Atlassian Marketplace. The time logging widget will automatically appear on all issue detail views.

Stuck

Ask a person.

If this guide does not answer your question, email us and a human answers. Name the product, what you were doing, and what happened instead. That is genuinely all we need to start.