Skip to main content
Version: 2.1.0

Changelog

Release 1.1.0 · Forge 2.1.0

New features

  • Site-wide global settings: new LogSense — Global Settings panel in Jira administration with General, Work Types, and Holidays tabs at site level. Spaces without their own configuration inherit global values; spaces with overrides keep their rules. Reset to Site Defaults restores site defaults.
  • Global → space inheritance: daily limit, default billable, work type catalog, and holiday calendar resolve at space level first, then from global configuration when no override exists.
  • Internationalization (EN/ES): LogSense UI (time logging, settings, gadget, and admin panels) displays in English or Spanish based on the user's locale in Jira, with English fallback.
  • eazyBI integration: when creating worklogs, LogSense adds a machine-readable stamp [LogSense:v1 billable=… type=…] to the Jira worklog comment (in addition to KVS persistence). New eazyBI tab in Global Settings with snippets for calculated fields.
  • Worklog backfill: documented procedure to update legacy worklog comments that only had metadata in KVS.

Release 1.0.0 · Forge 2.0.0

✨ Main Features:

  • Time tracking provider (Preview): Activate LogSense in Settings → Work items → Time tracking to replace the native Log work UI. Logging is available from the Log work action, Work log tab, and provider administration.
  • Enriched time logging: Form with date picker, time shortcuts (15m, 30m, 1h, 2h, 4h), progress bars for issue estimate and daily limit, and billable/non-billable, work type, and notes fields.
  • Daily hour limit: Validates the total logged per user and date within the space, with fail-safe behavior when verification is temporarily unavailable.
  • Per-space settings (LogSense Settings): New tab in space navigation with general settings (daily limit, default billable, estimates, and holiday blocking), work type catalog, and holiday calendar.
  • Billable hours gadget: Displays billable and non-billable hours on Jira dashboards from worklogs logged with LogSense.