Logging time with LogSense

When LogSense is active as the time tracking provider, time is logged from the issue Log work action. In this release the modal shows duration shortcuts as buttons, highlights the one that matches the typed duration, and the daily limit indicator no longer shows 0m: if the space has no cap, the indicator is not displayed.

Open the logging form

From Log work action

1. Open an issue in Jira.
2. In the actions menu (⋯) or action bar, select Log work. The Log work modal opens.

Form fields

Field	Description
Date	Calendar date picker (DatePicker), respecting user locale.
Time spent	Manual duration or shortcuts.
Billable	Billable / non-billable classification.
Work type	Effort category (space catalog: active default types + custom types).
Notes	Entry comment. Supports multiple lines and basic formatting (Forge UI / Custom UI).

Time shortcuts

To speed up logging, the form offers five shortcuts as buttons, under Quick durations: 15 min, 30 min, 1 hour, 2 hours, and 4 hours.

• Clicking a shortcut applies its value to the Time spent field. You can adjust it manually afterward.
• The shortcut that matches the typed duration is highlighted, whether you clicked it or typed that value by hand.
• If the duration does not match any shortcut (for example, 45m), none is highlighted.

Progress bars

The form shows two visual indicators:

Issue estimate

Bar relating time already logged on the issue to its original estimate (if any).

Daily limit

Indicator of the space's daily limit for the current user on the selected date. The label names the space the limit belongs to (for example, Daily limit · SIT). LogSense calculates the total by aggregating the current user's worklogs for the day in the space.

What it shows depends on the space configuration and the time already logged on that date:

Situation	What you see
The space has no daily limit	The indicator is not displayed. No "no limit" text or 0m appears.
There is a limit and no time yet on the date	The message No time logged today. and the maximum (for example, 8h max). 0m / 8h is not shown.
There is a limit and time is already logged	The hours logged and the hours still available for the day (for example, 2h logged · 6h remaining today.).
The limit has been reached	The indicator shows that the daily limit has been reached.

The indicator only changes the presentation: the limit validation on save is the same (see Daily limit validation).

Fail-safe behavior

If Jira cannot verify the daily limit (API error or permissions), LogSense allows logging to avoid blocking users due to transient failures.

Daily limit validation

On save, LogSense checks that the new entry does not exceed the daily limit configured in Space settings → LogSense Settings → General. If it does, the form shows an error and does not save until duration or date is corrected.

Holiday validation

If the space has holiday blocking active and the selected date is a holiday, the entry is rejected. Check with the space administrator in Space settings → LogSense Settings → Holidays.

Validation by status and work item type

If the administrator configured Active Status or Active Work Item Types in the space (Space settings → LogSense Settings → Logging rules), LogSense validates that the issue state and type are in the allowed list before allowing logging or editing. If they are not, the form shows a clear message explaining why the action is blocked.

Inheritance and overrides

Active status and types are configured per space and can inherit site values. If you see an unexpected block, contact the space administrator.

Billing period validation

If the entry date falls in a closed billing period, LogSense prevents saving the entry or applying the edit and shows a clear message. Ask the space administrator to review the period state in Space settings → LogSense Settings → Billing if you need to log or edit work in that range.

Rich Notes

The Notes field supports multiple lines and basic formatting (bold, italics, lists, and line breaks) according to Forge UI / Custom UI capabilities. When reviewing a worklog from the Work log tab or the side panel, the formatted content is displayed correctly, including line breaks and styles.

Collapsible notes

When notes are not required, the editor starts collapsed to keep the form shorter:

• Add notes opens the editor.
• Hide notes collapses it. The text you typed is kept and reappears when you open it again.
• If there is already text, the action shows as Edit notes.
• When editing a worklog that already has a note, the editor opens expanded.

Relationship with Require notes

Rich formatting always applies when notes are shown. If the administrator enabled Require notes, the editor is always expanded (it cannot be collapsed), still supports multiple lines and formatting, and you must complete it to save.

Save the entry

1. Complete required fields (if Require notes is active, the Notes field is required and shows an asterisk *).
2. Review progress bars if applicable.
3. Confirm with Save / Log work.

Metadata (billable, work type) is stored in Forge KVS associated with the Jira worklog.

Edit an existing worklog

From version 2.3.0, LogSense allows editing existing worklogs without deleting and recreating them.

1. Open an issue in Jira.
2. In Activity → Work log tab, locate the entry to edit.
3. Select Edit from the worklog actions.

A form will open with the previously entered data, where you can modify the necessary fields.

Editable fields

Field	Description
Date	Entry date (calendar picker).
Time spent	Manual duration or shortcuts.
Billable	Billable / non-billable classification.
Work type	Effort category (space catalog).
Notes	Entry comment, multi-line and formatted (required if Require notes is active).

Validations when editing

• Daily limit: verifies the new value does not exceed the configured limit.
• Holidays: if the edited date is a holiday and blocking is active, editing is rejected.
• Issue status and type: if the issue state or type is no longer in the active list, editing is rejected.
• Billing period: if the edited date falls in a closed period, editing is rejected.
• Issue estimate: the progress bar updates after saving.
• Permissions: if you don't have EDIT_OWN_WORKLOGS or EDIT_ALL_WORKLOGS, the Edit button does not appear.

Required Notes behavior

If the administrator enabled Require notes in global or space configuration, the Notes field is mandatory both when creating and editing. The form shows:

• Label with asterisk (*)
• Placeholder without "optional"

If you try to save without completing Notes, the form shows an error and won't proceed.

Required Jira permissions

Permission	Effect
EDIT_OWN_WORKLOGS	Allows editing only the current user's worklogs.
EDIT_ALL_WORKLOGS	Allows editing any worklog in the project.
No edit permissions	The Edit button is not shown.

Worklog approval states

From version 2.4.0, new worklogs can go through an approval workflow before becoming effective for LogSense.

What each status means

Status	Icon	Counts in LogSense?
PENDING	⏱ (clock)	No
APPROVED	✓ (check)	Yes
REJECTED	✗ (cross)	No

Who can approve or reject?

Only users on the space's approver list (configured by the administrator in Space Settings → LogSense Settings → General) can change a worklog's status by clicking the clock icon ⏱ on a PENDING worklog to open a modal where they can approve or reject, with the option to add a comment.

Worklogs before v2.4.0

Worklogs recorded before this version do not have an approval status. LogSense treats them as APPROVED automatically for backward compatibility.

Administrator configuration

See Approver configuration in the administrator guide.

More information

• Billable and work types
• Issue panel as visual summary
• Worklog approval workflow
• Hours report and timesheet