Aller au contenu principal

Connect 05.08.2026

· 3 minutes de lecture

Features and Fixes for Time Tracking and Project & Resource Planning

DYCE Time Tracking

Features

  • A new Billing Disposition field classifies how the effort on a Work Order should be treated for billing, for example as invoiceable or as a warranty case, so that the project manager has this context when releasing time recordings in Business Central. The field is available on the Work Order card and as an (initially hidden) column in the Work Orders list. The selectable values are defined centrally in Business Central, so the same list is offered in Time Tracking and in Jira. On Work Orders that originate from another system, the field is shown read-only.
  • Surcharges now take the Base Calendar of the project into account when classifying a day. If the Surcharge Model specifies the project as the source of the calendar, that calendar decides whether a day counts as a working day, otherwise the resource's calendar is used, and if neither is set the day of week applies as before.

DYCE Time Tracking for Jira (Forge app)

Administrator approval required

This version of the Forge app requests an additional permission ("delete project property"). Jira does not roll out an app update with widened permissions on its own: a Jira administrator has to approve it under Apps in the Jira administration. Until that approval, the previous version of the app stays installed and the new features described below are not available.

Features

  • The Billing Disposition is available as a Jira custom field that can be set on a work item and searched via JQL. Its options come from Business Central. In the space settings, a default Billing Disposition can be defined per space and, optionally, per work item type.
  • A new Get Work Order Jira automation action reads the Work Order currently assigned to a work item and provides its data as smart values, for example Work Order number, title, customer, project, budget type, resource, status, and the assigned Billing Work Order. The data is read live, and the action reports whether a Work Order exists at all. Because Jira limits the number of outputs per action, the values are spread across three actions that can be combined as needed.
  • A new Jira automation action triggers the work log synchronization for an entire space, so a sync can be scheduled or attached to an existing automation rule instead of being started by hand.
  • The Billing Work Order Types setting in the space settings is now saved explicitly with Save and Close buttons, making it clear when a change has been applied.
  • Client keys left behind by the previous Connect version of the app are now removed automatically after the switch to the Forge app. The cleanup runs in the background when the app settings are opened and retries later if a space could not be processed. It is the reason for the additional permission mentioned above.

Fixes

  • The time and duration fields and the Advanced button in the time recording dialog can now be used immediately, instead of staying blocked until the initial mapping has finished loading.

DYCE Project & Resource Planning

Fixes

  • Fixed drag & drop in the calendar view not working in Mozilla Firefox. Work Orders can now be moved in the calendar in Firefox as in the other supported browsers. (SD-443)