Jira Log

b.jira now includes a dedicated Jira Log table, providing administrators with a comprehensive overview of all synchronization runs at a glance. The log captures key details such as the time and duration of each sync, giving you valuable insight into synchronization performance and helping you identify potential bottlenecks or irregularities over time. This addition makes it easier than ever to monitor the health and efficiency of your Jira-Business Central integration on an ongoing basis.

Incorrect Parent Issue Assignment

Resolved an issue where, under certain circumstances, the parent issue of a Jira work item could be incorrectly assigned when synchronized to Business Central. This could result in issues being linked to the wrong parent, leading to inaccurate hierarchical relationships in your BC data. The fix ensures that parent-child relationships between issues are now correctly resolved and maintained throughout the synchronization process.

Automatic Removal of Deleted Jira Issues

Issues / work items that have been deleted in Jira are now automatically removed from Business Central as part of every synchronization run. Previously, deleted Jira issues would remain as orphaned records in BC, requiring manual cleanup to keep both systems in sync. This improvement ensures that your Business Central data always accurately reflects the current state of your Jira environment, reducing data clutter and improving overall consistency across both platforms.

Spurious Empty Sales Documents

Resolved a rare but critical issue where empty sales documents could be created unintentionally under certain circumstances. While the occurrence was infrequent, the impact could be disruptive, requiring manual cleanup of affected records. This fix ensures that sales documents are only created when all required data is present and valid, preventing empty records from appearing in your Business Central environment.

Log Retention Policy

b.jira now includes a configurable log retention policy, allowing administrators to control how long synchronization and activity logs are kept before being automatically cleaned up. The setting can be found directly in the Business Central Jira Setup and defaults to a retention period of one month out of the box. This addition helps keep your environment tidy and prevents unnecessary accumulation of log data over time, while still giving you the flexibility to adjust the retention period to match your organization's specific requirements.

Improved Tempo Accounts Stability

Tempo Accounts handling has been thoroughly revised and further stabilized in this release, resulting in a more robust and dependable experience when working with account-related data. Particular attention was given to the interaction between Tempo Accounts and Tempo Account Categories, which could previously lead to inconsistencies during synchronization. These edge cases have been addressed, ensuring that Tempo Accounts and their associated categories are now synced correctly and reliably across all supported configurations.

Partial Synchronization Option

b.jira now offers the ability to perform a partial synchronization, giving you more granular control over which data is included in a sync run. This option can be found on the Synchronization page and is hidden by default to keep the interface clean for standard use cases. When needed, it can be revealed and configured to limit the scope of a synchronization — useful for targeted updates or troubleshooting specific data areas without triggering a full sync.

Float Number Custom Field Handling

Resolved an issue where custom fields of type float number could cause unexpected behavior under certain configurations. Affected users may have experienced incorrect values or sync errors when working with decimal-based custom fields. This fix ensures that float number custom fields are now handled reliably across all supported configurations.

Improved Sync Progress Dialog

b.jira now features a redesigned synchronization progress dialog that gives you full visibility into every step of the sync process. The dialog provides a detailed, real-time breakdown of all data categories being synchronized — from Users, Projects, and Issues through to Tempo-specific data such as Worklogs, Accounts, and Worklog Approvals. Each item is clearly marked as completed, in progress, or pending, so you always know exactly where the sync stands at a glance. This improvement makes it significantly easier to monitor long-running synchronizations and quickly identify any areas that may require attention.

Tempo Projects

b.jira's support for Tempo Projects has been significantly improved and stabilized, delivering a more reliable and seamless experience when working with consolidated project structures. Tempo Projects allow you to bring together multiple Jira projects and issues under a single umbrella, making it easier to track and manage work across team boundaries. With this update, syncing and displaying Tempo Project data within b.jira is now more consistent and robust than ever. For more information on what Tempo Projects can do for your workflow, visit the Tempo website.

Set project not invoice relevant

A project can now be marked as not invoice relevant. Workloads for these projects will automatically be cancelled.

Estimate localization issue

Time estimates were not correctly localized in some cases.

Time estimate calculation in sales order assignment

In some cases the time estimates were not correctly calculated.

Synch issues regardless of project status

Issues are now always synched when modified, even if the project was not modified.

Added support for text area custom fields

Text Areas are now supported in custom fields.

Validate Sales Document Link

Execute validation trigger when setting the sales document link.

Tempo Approval Type

The Tempo Approval Type (Timesheet, or Project) as well as the approval period, can now be set on Jira Setup.

Credit memo Quantity

In some cases the quantity in the credit memo was not correctly updated after editing the worklogs.

Various bug fixes and performance improvements

Set Split Document Lines by on Project

It is now possible to configure a separate splitting of sales invoice lines directly within the Jira Project.
This means that the way invoice lines are split no longer has to follow the rules defined in the customer setup.
With this improvement, projects can apply their own logic for invoice line distribution, giving you greater flexibility and control when billing out of Business Central through Jira.
This is especially useful when different projects for the same customer require different invoicing structures, or when project-based reporting and transparency demand a custom approach.

Tempo Approval period support

A new field has been added to the Jira Setup that lets you define which type of approval period is used in Tempo.
You can now choose between weekly or monthly approval periods, depending on your organization’s needs.
This provides greater flexibility in aligning approval cycles with reporting, payroll, or project billing requirements.
By setting the approval period type directly in Jira Setup, you can ensure that the time approval process in Tempo is consistent and tailored to each business scenario, while also reducing the need for manual adjustments.

Removed deprecated fields from pages

Switch to new JQL endpoint

Switch from deprecated JQL endpoint to new endpoint.

New events in Worklog Management Codeunit

Added new integration events to BMSJiraWorklogManagement

Performance optimization

Only necessary fields will be synchronized for Jira issues.

Sales integration: Improved Hour Calculation for Sales Order Lines

Resolved an issue where specific unit of measure configurations could lead to incorrect hour calculations on sales order lines. The calculation now consistently respects the defined unit conversions, ensuring accurate time tracking across all scenarios.

Sales integration: Corrected Processing Type Determination on Jira Worklog Page

Addressed an issue where the Processing Type on the Jira Worklog page was occasionally not calculated correctly. The logic has been refined to ensure consistent and accurate assignment based on the worklog context.

Sales integration: Create Jira Issues Directly from Sales Lines

You can now create Jira issues directly from sales lines using the new “Create Jira Issues for Sales Lines” action, available on the sales order subpage.When triggered, the system will prompt the user to fill in all mandatory Jira fields (e.g., issue type). Sales lines can be assigned to different Jira projects as needed — there’s no requirement to link all lines to the same project.Once a Jira issue has been successfully created and linked, the corresponding sales line will no longer be available for selection in future issue creations. To create a new Jira issue from an already assigned line, simply clear the Jira Issue Code field in the sales line manually.

Sales integration: Consistent Assignment of Child Issues to Sales Lines

Resolved an issue where child Jira issues (e.g., tasks under an epic) were not always automatically linked to the same sales line as their parent issue. The system now reliably inherits the sales line assignment from the parent, ensuring consistent traceability.

Always synch all projects

A new option “Always synchronize Projects“ was added to the Jira Setup. When active, the synchronization will synchronize every project from Jira. When deactivated (default), the synchronization will only synchronize projects from Jira that include recently changed / added Issues.