Frequently Asked Questions
Do I need to activate LogSense as the time tracking provider?
Not required to install the app, but yes for the full experience: Log work modal and Work log tab with LogSense metadata.
What happens to worklogs logged before installing LogSense?
Existing native worklogs remain in Jira. They won't have billable/work type metadata in KVS until edited or replaced with new LogSense entries. Worklogs before v2.1.0 may lack the eazyBI stamp in the comment; see backfill in eazyBI integration.
How is the daily limit calculated?
LogSense sums worklogs for the current user on the selected date within the space, using JQL (worklogAuthor = currentUser(), worklogDate) and paginated API queries. The effective limit comes from the space or, if there is no override, from site-wide global settings.
What if the API fails when verifying the limit?
The app applies fail-safe behavior: it does not block logging due to a transient API error. The limit will be validated again on later attempts when the API responds.
Can I log time on a holiday?
Only if the space does not have holiday blocking enabled, or if the date is not in the Holidays calendar (space or inherited from site). With blocking active, the form rejects holiday dates.
Are work types global?
From version 2.1.0, you can define a global catalog in LogSense — Global Settings and per-space overrides in LogSense Settings. A space without its own catalog inherits site work types.
Where do I configure LogSense Settings?
In version 2.2.0, in Space settings → LogSense Settings. Site-wide global configuration is under Jira Administration → Apps → LogSense — Global Settings or via Connected apps / Configure when Atlassian exposes that route.
How do I report billable and work type in eazyBI?
LogSense writes a [LogSense:v1 billable=1 type=development] stamp in the worklog comment. Configure calculated fields in eazyBI to parse it. See eazyBI integration.
What language is the UI shown in?
LogSense adapts labels, buttons, and messages to the user's locale in Jira (English or Spanish). If a translation is missing, the app falls back to English. Work type names defined by administrators are configuration data, not app strings.
Does the gadget show only billable hours?
The reporting gadget focuses on billable hours. It may include non-billable comparisons depending on gadget UI configuration.
What is the difference between Billable hours and Pending approvals?
Billable hours displays the monthly billable-hours report for a space and identifies tickets whose total LogSense time exceeds their original estimate. Pending approvals displays worklogs awaiting approval and lets authorized users act on them from the dashboard.
How do I configure the Billable hours gadget?
Select a Space and Month in the gadget configuration. After you save, the report loads automatically when you open the dashboard. You no longer need to enter a From/To range or click Generate on every visit.
Do PENDING worklogs count when identifying tickets that exceed the estimate?
No. PENDING worklogs do not count in Logged or LogSense calculations until they are approved. APPROVED worklogs are included in this calculation.
Who can approve from Pending approvals?
Only users included in the space's approver list can use the Approve and Reject actions. Other users can see the status, but cannot change it.
Can I edit an existing worklog?
Yes, from version 2.3.0. You can edit existing worklogs in the issue panel and in the Work log tab. Editable fields are: time, date, work type, billable, and notes. Editing is subject to Jira permissions: you need EDIT_OWN_WORKLOGS to edit your own entries and EDIT_ALL_WORKLOGS to edit any worklog.
What happens if I try to edit a worklog without permission?
If you don't have EDIT_OWN_WORKLOGS or EDIT_ALL_WORKLOGS, the Edit button does not appear. If you try to edit through other means, LogSense shows an error saying you don't have sufficient permissions.
What are required Notes?
From version 2.3.0, administrators can enable Require notes in global or per-space configuration. When active, the Notes field becomes mandatory: you cannot create or edit a worklog without filling it. The form shows an asterisk (*) on the label and the placeholder no longer says "optional". If you try to save without notes, the form shows an error and won't proceed.
Where is Require notes configured?
In the General tab of LogSense — Global Settings (site level) and LogSense Settings → General per space. Global configuration acts as the default; each space can override it. It is disabled by default (optional).
Which LogSense modules depend on the time tracking provider?
The following modules are only visible when LogSense is selected as the time tracking provider in Settings → Work items → Time tracking:
- Log work issue action
- Work log tab
- LogSense side panel (time logging UI)
The following modules do not depend on the provider and are always accessible:
- LogSense — Global Settings (administration)
- LogSense Settings per space (Space settings)
- Billable hours gadget (dashboards)
- Pending approvals gadget (dashboards)
- v2.3.0: the panel only shows when LogSense is the active provider (visibility fix).
- v2.4.0: the panel is redesigned as a visual summary (KPIs, alerts, latest entries) and no longer includes worklog editing/deletion.
Why does the side panel no longer allow editing/deleting worklogs?
To avoid UI duplication and reduce complexity, the side panel was redesigned as a read-only dashboard. Edit and delete actions are available in the Work log tab and require native Jira permissions.
What are the PENDING / APPROVED / REJECTED approval states?
From version 2.4.0, new worklogs can go through an approval workflow:
- PENDING: awaiting approval. Does not count toward LogSense totals, reports, panel, gadget, or activity.
- APPROVED: approved. Counts normally toward all LogSense totals and reports.
- REJECTED: rejected. Does not count toward totals. The worklog exists in Jira but LogSense excludes it from calculations.
Worklogs before v2.4.0 without an approval status are treated as APPROVED for backward compatibility.
Who can approve or reject worklogs?
Only users whose accountId is in the space's approver list (configured in Space Settings → LogSense Settings → General) can change the status from PENDING to APPROVED or REJECTED. Users outside this list see the clock icon ⏱ (indicating it is pending) but cannot interact with it.
How do PENDING and REJECTED states affect LogSense totals?
Worklogs in PENDING and REJECTED states are not included in:
- Side panel KPIs
- Billable hours gadget reports
- Activity / Work log tab (LogSense totals)
- Provider / time tracking (LogSense calculations)
Who appears as the worklog author after approval?
The worklog is already created in Jira when it is logged (with the original logger as author). From version 2.5.0, that author is kept on approval: it is not reassigned to the approver.
In what order are worklogs displayed?
From version 2.5.0, the list is sorted by the Date column (date worked) in descending order: newest first.
What happens to worklogs recorded before v2.4.0?
Worklogs before version 2.4.0 do not have the approvalStatus field. LogSense treats them as APPROVED automatically, so they continue to count toward totals without requiring migration.
Does LogSense work in Jira Service Management?
Yes, on any Jira Cloud site where the app is installed and time tracking is enabled, including JSM spaces that use worklogs.
What happens if Jira responds with a 503 error when loading an issue?
From version 2.5.0, LogSense automatically retries temporary Jira errors (such as 503). If the problem persists, it shows a clear message and a Retry button, preventing you from seeing unformatted technical errors.
How do I get support?
Contact support@mbgroup.pe or MB Group's usual support channels.