Changelog

Release 1.5.1 · Forge 2.7.0

🔒 Security and maintenance

• Preventive internal dependency updates: resolved two critical-severity and sixteen high-severity findings in build dependencies, with no impact on time logging, gadgets, or approvals.
• No functional changes: worklogs, the approval workflow, dashboard gadgets, and the Billable hours report remain unchanged.
• Direct upgrade: compatible with Forge 2.6.0; no migration or administrator action is required.

Release 1.5.0 · Forge 2.6.0

✨ New features

• Pending approvals gadget: approvers can review pending worklogs from one or more spaces on a dashboard and approve or reject them without opening each issue.
• Monthly Billable hours report: the gadget lets users select a space and month, saves that configuration, and loads the report automatically when the dashboard opens.
• Tickets that exceed the estimate: the Billable hours gadget now includes a section showing tickets whose total LogSense time exceeds their original estimate.

🔧 Behavior changes

• Dashboard actions: when a worklog is approved or rejected from Pending approvals, the row disappears, the count is updated, and the pending indicator in the Billable hours report is refreshed.
• Estimate comparison: PENDING worklogs do not count toward logged time until they are approved. The comparison uses the ticket's total LogSense time against its original estimate.

Release 1.4.1 · Forge 2.5.0

✨ New features

• Loading indicator in the review modal: the approval/rejection modal now shows a loading indicator while processing the action, improving visual feedback.

🐛 Fixes

• Internal comments in JSM on approve/reject: automatic comments when approving or rejecting a worklog are now correctly posted as internal in Jira Service Management spaces, visible to the team only.
• User-friendly message and retry when loading an issue fails: on temporary Jira errors (e.g. 503), LogSense automatically retries and, if it cannot recover, shows a clear message with a Retry option.
• Notes field visual alignment: fixed the alignment of the Notes field in the time logging form.
• Worklog author incorrectly reassigned on approval: fixed a bug where the worklog author was reassigned to the approver instead of remaining as the person who logged the time.
• Worklogs sorted by date worked: worklogs are now sorted by the logged date (started) in descending order (newest first).

Release 1.4.0 · Forge 2.4.0

✨ New features

• Issue panel as visual summary: the LogSense side panel is redesigned as an issue metrics dashboard: KPIs (total logged, billable / non-billable, % billable), work type breakdown with horizontal bars, estimate vs spent bar. Detailed management (create/edit/delete) remains exclusively in the Work log tab.
• Worklog approval (PENDING / APPROVED / REJECTED): new worklogs start in PENDING state and do not count toward LogSense totals or reports until APPROVED. REJECTED worklogs are excluded from totals. Approvers are configured per space in Space Settings.

🔧 Behavior changes

• Side panel — summary only: the side panel no longer includes a worklog table with edit/delete, its own form, or redundant issue key/summary. Use the Work log tab for detailed management.

Release 1.3.0 · Forge 2.3.0

✨ New features

• Worklog editing: you can now edit existing worklogs from the issue panel and Work log tab, without deleting and recreating them. Editable fields include time, date, work type, billable, and notes. Editing respects Jira permissions — if you don't have edit rights, the button is not shown.
• Required Notes: administrators can enable Require notes in global or per-space configuration. When active, the Notes field is mandatory both when creating and editing a worklog.
• Official logo: the official LogSense for Jira logo is now used in the documentation and application materials.

🐛 Fixes

• Side panel hidden without LogSense as provider: the LogSense side panel no longer appears when LogSense is not the active time tracking provider, removing the inconsistent UI.
• Security updates: dependencies were updated to mitigate a CRLF injection vulnerability.

Release 1.2.0 · Forge 2.2.0

✨ New features

• LogSense Settings in Space settings: per-space configuration leaves the main space navigation and moves into Space settings, so only space administrators manage settings such as daily limit, default billable, work types, and holidays.
• Restored admin access: documentation now covers access to the global LogSense panel from Jira Administration → Apps and from Connected apps / Configure, aligned with recent Atlassian navigation changes.
• CI with lint and tests: the project now includes automatic validation in Bitbucket Pipelines to run npm ci, npm run lint, and npm test before merge/deploy.

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.