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.
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.
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. With blocking active, the form rejects holiday dates.
Are work types global?​
In version 1.0.0, the catalog is per space (Work Types tab in LogSense Settings). Site-wide global configuration arrives in v1.1.0.
Where do I configure LogSense Settings?​
In version 1.0.0, in space navigation → LogSense Settings. Space settings location is planned for v1.2.0.
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.
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 projects that use worklogs.
How do I get support?​
Contact support@mbgroup.pe or MB Group's usual support channels.