LogMyTime — Documentation

For LogMyTime on Jira Cloud · Contact: support@bazoho.com

LogMyTime lives in two places in Jira: the LogMyTime app (Apps menu → LogMyTime) where everyone logs and submits time, and LogMyTime Configuration (Jira settings → Apps) where admins set up teams, schedules, holidays and attributes.

Contents

• Getting started
• Logging time
• The timesheet grid
• Submitting & approvals
• Approving others' timesheets
• Shift patterns & schedules (admin)
• Holiday calendars (admin)
• Work attributes (admin)
• Native Jira worklogs: import & mirror
• Exporting data
• App settings (admin)
• Troubleshooting & FAQ

Getting started

After an admin installs LogMyTime from the Atlassian Marketplace:

• Open the app: in Jira, click Apps in the top navigation → LogMyTime.
• Admin configuration: click the settings gear → Apps → LogMyTime Configuration in the left sidebar.
• Quick log from an issue: open any Jira issue and use the Log time panel.

Admins should set up at least a shift pattern (so required hours appear) and, for multi-country teams, holiday calendars. Everything else works out of the box.

Logging time

Open Apps → LogMyTime and use the My Timesheet tab. Click any day cell for an issue to open the editor, then add a worklog:

• Duration accepts flexible formats: 1.5, 1:30, or 1h 30m.
• Add an optional description and, if your admin configured them, pick Activity (or other attribute) values.
• + Add issue searches your Jira issues; + New issue opens Jira's create dialog and drops the new issue straight into the grid.
• Pin an issue (pin icon on its row) to keep it on every week and month, even before you log against it.

You can also log from the Log time panel on any Jira issue.

The timesheet grid

• Switch between Week and Month; use the arrows, Today, or the calendar icon to jump to any period.
• The footer shows logged vs required hours per day and for the period — green when met, amber when under.
• Holiday columns are tinted purple (hover for the holiday name); required hours drop automatically on holidays.
• View by re-pivots the grid: by issue, by an attribute (e.g. Activity), or nested (issue › Activity, or Activity › issue).
• Click an issue key to open it in a Jira popup without leaving the sheet.

Submitting & approvals

When your period is complete, click Submit (add an optional note). Submitting locks those entries and snapshots your logged and required totals.

• Flexible mode (default): you can Reopen your own submitted sheet at any time to edit and resubmit.
• Strict mode: only an approver can send a submitted sheet back.
• Once approved, reopening always requires an approver or admin.
• You can still add or change time on a submitted/approved period, but those changes are flagged — you and your approver both see a banner and the affected entries are highlighted, prompting a reopen and resubmit so totals stay honest.

Approving others' timesheets

Approvers use the Approvals tab. It lists timesheets waiting for you and, below, those you approved in the last 13 weeks.

• Review opens the full grid (with the same View-by pivots) plus a per-day list of entries.
• Approve, or Reject with a required comment (the sheet returns to the owner to fix and resubmit).
• Reopen an approved sheet when corrections are needed.
• A changed chip marks any sheet whose hours moved after submission.

Approvers are set per team (or via a per-user override) in configuration. Approvers cannot approve their own timesheets; Jira admins can, as an escape hatch for small teams.

Shift patterns & schedules (admin)

In LogMyTime Configuration → Shift patterns, a pattern is a repeating cycle of days that defines required hours.

• Use a preset (Mon–Fri 9–17 or 4 on / 4 off nights) or build your own: set each day as working or off, its start/end times, whether it crosses midnight, and required hours.
• Edit a pattern anytime — changes apply going forward; already-submitted timesheets keep their snapshot totals.
• Assign a pattern to a user or a whole team, with an anchor date (the date that is day 0 of the cycle) and an effective-from date. Manage or end assignments in the same panel.

Night shifts that cross midnight attribute early-morning work to the shift's start day, and required hours stay correct across timezones and daylight-saving changes.

Holiday calendars (admin)

In Configuration → Holidays:

• Create a calendar (e.g. "Mauritius", with an optional region code), then add holidays individually or paste CSV lines YYYY-MM-DD,Name[,fraction] (fraction 1 = full day, 0.5 = half day).
• Assign a calendar to a person or a whole team. Holidays apply per person, so a Mauritius team and a German team can share one Jira site and each see their own.
• On a holiday, that day's required hours are reduced (to zero for a full day, halved for a half day) and the column is highlighted in the grid.

Work attributes (admin)

In Configuration → Work attributes, define dropdowns people fill when logging — for example Activity with options Implementation / Testing / Support.

• Set a default option per attribute; it is applied automatically to worklogs imported from Jira.
• Attributes and options are deactivated, never deleted, so historical worklogs keep their labels.
• In the timesheet, values appear as chips and can be pivoted with View by; approvers see the same breakdown.

Native Jira worklogs: import & mirror

Two optional, independent flows keep LogMyTime and Jira's native worklogs in sync (both set in Configuration → Settings):

• Import (on by default): time logged with Jira's own "Log work" button is pulled into LogMyTime, tagged as imported and given each attribute's default value.
• Mirror (off by default): worklogs created in LogMyTime are copied to native Jira worklogs, so Jira reports and burndowns stay accurate.

Entries are de-duplicated so nothing is counted twice, and locked (submitted/approved) periods are never silently changed.

Exporting data

The Export tab produces a CSV that opens in Excel:

• Quick ranges from Today to Last year, or a custom date range.
• Scope: your own time; your team (for approvers); or everyone (for Jira admins).
• Columns: date, user, account ID, issue, summary, hours, billable hours, description, origin, timesheet status, and one column per work attribute.

App settings (admin)

Configuration → Settings controls:

• Approval mode — flexible (owners can reopen their submissions) or strict.
• Import native Jira worklogs — on/off.
• Mirror worklogs to Jira — on/off.
• Grace days — how long after a period ends before overdue reminders appear.
• Storage diagnostics — a readout of data usage against the platform's per-install limit.

Troubleshooting & FAQ

I can't find the app. Hard-refresh Jira (Ctrl/Cmd+F5). The app is under Apps → LogMyTime; the admin page is under Jira settings → Apps → LogMyTime Configuration (in the left sidebar).

Required hours show 0. Assign a shift pattern to the user in Configuration → Shift patterns.

A holiday isn't reducing hours. Check the user has the right holiday calendar assigned, and that the holiday's date falls on a working day in their pattern.

The app is read-only. The subscription is inactive — you can still view and export data. A Jira admin can renew it via Atlassian billing.

Reporting a problem. Email support@bazoho.com with your Jira site URL, what you did, what you expected, what happened, and the build stamp shown in the app footer / configuration header. See also our support page.