Site-wide global settings

From version 1.1.0, site administrators can define site-level default values that spaces inherit or override. This avoids repeating the same configuration in every space.

Access

1. Sign in with Jira Administrator or Site Administrator permissions.
2. Open Jira Administration (⚙️).
3. Go to Apps → LogSense — Global Settings.

You can also reach it from Settings → Work items → Time tracking when LogSense is the active provider, via the LogSense configuration link. On some sites, Atlassian also exposes this access through Connected apps / Configure.

Available tabs

The LogSense global configuration screen mirrors LogSense Settings per space, with four tabs:

Tab	Content
General	Site-level daily limit, default billable, estimates, and holiday blocking.
Work Types	Global work type catalog inheritable by spaces.
Holidays	Global holiday calendar inheritable by spaces.
eazyBI	Instructions and snippets for external reporting. See eazyBI integration.

General tab

The options match LogSense Settings — General, but apply as site defaults:

• Daily hour limit
• Default billable
• Estimates
• Holiday blocking

Work Types tab

Define the work type catalog that spaces without their own override use when logging time.

Holidays tab

Configure corporate or national holidays that spaces can inherit when they have no local calendar.

Global → space inheritance model

LogSense resolves effective configuration per space with this priority:

1. Space configuration — if the space has saved its own values, they take precedence.
2. Site global configuration — if the space has no override, it uses global defaults.
3. App internal defaults — only when neither global nor space configuration exists.

Scenario	Behavior
New space without LogSense Settings	Inherits daily limit, work types, holidays, and default billable from the site.
Space with its own configuration	Keeps its override; global settings do not overwrite it automatically.
Reset to Site Defaults in the space	Removes the space override and restores site values (not hardcoded app defaults).

Where to configure each space

In version 1.2.0, per-space LogSense Settings live in Space settings (jira:projectSettingsPage). Only users with space administration permissions should be able to modify this configuration.

Best practices

• Define corporate holidays and standard work types globally.
• Reserve per-space overrides for exceptions (e.g. a client space with a different daily limit).
• After changing global settings, review critical spaces that rely on inheritance before month-end close.

Next steps

• LogSense Settings — General — per-space override
• eazyBI integration — reporting with worklog metadata