Release 2.5.0, featuring improved repository restore workflow, updated Microsoft 365 backup engine, and enhanced logging for custom action scripts.
Improved replication task initialization performance and resource efficiency. Replication task initialization is now significantly faster when the target storage already contains existing data, while simultaneously reducing peak CPU and memory consumption. For cyclic replication scenarios, this optimization accelerates task execution by up to 66 times (e.g., reducing initialization time from 12 hours to 11 minutes), maintaining a stable infrastructure load without compromising data restore capabilities from replicated storage.
Updated Microsoft 365 backup and restore engine to Microsoft Graph API. GitProtect now uses the Microsoft Graph API instead of legacy Exchange Web Services (EWS) to process Microsoft 365 email messages, contacts, and calendars. This architectural transition ensures long-term service compliance and stability ahead of Microsoft's October 2026 EWS deprecation while accelerating backup and restore throughput. The update is fully backward-compatible with existing EWS-created backups and enhances item-level recovery fidelity by preserving message properties, categories, and attachment integrity. Additionally, optimized pagination and duplicate detection resolve stability issues during recovery across all backup types.
Updated management panel task execution logic to consistently respect GitProtect Management Service concurrency limits. The management panel now strictly enforces maximum concurrent backup task limits returned by GitProtect Management Service across all backup plan types. This change eliminates legacy environment-specific caps and hard-coded constraints, ensuring the panel correctly applies configured defaults (5 concurrent tasks for cloud, 20 for on-premises) and fully honors custom values defined via the XOPERO_MAX_CONCURRENT_BACKUP_TASKS environment variable.
Updated AES-256 encryption warning display behavior in backup plan configurations. GitProtect no longer displays the AES-256 encryption warning for workloads such as Microsoft 365 to eliminate unnecessary user confusion regarding features not applicable to those configurations.
Improved custom action script execution logging for backup and replication tasks. GitProtect now logs the execution progress and output of custom action scripts across Windows and Linux backup agents (workers). Execution logs track script initiation, completion status, and console output, providing complete visibility into pre- and post-task operations, while ensuring that sensitive data such as passwords remain masked in the logs.
Improved Jira and Confluence backup browsing performance. GitProtect now utilizes a metadata caching mechanism to accelerate browsing and enhance reliability when preparing Jira and Confluence backups for restoration. This update eliminates timeout issues in large enterprise organizations, introduces real-time visual progress indicators during data loading, and guarantees accurate synchronization status feedback regardless of backup retention age.
Improved repository restore workflow with enhanced destination controls and validation. GitProtect now gives administrators clearer visibility and control over restore destinations during repository recovery. This update separates custom repository naming from target path selection, enforces strict organization and repository naming rules, and introduces clear in-app notification guidance detailing fallback behaviors across GitHub, GitLab, and Azure DevOps environments.
Fixed an issue where the Intel-based macOS backup agent failed to start and register after installation. The agent now starts correctly following installation and successfully registers with the GitProtect Management Service. Previously, initialization on Intel-based macOS devices failed without generating diagnostic logs.
Fixed an issue where remote updates failed on GitProtect Linux backup agents due to library dependencies. The agent now completes remote updates successfully and remains online throughout the entire upgrade process. Previously, remote updates could fail when restarting the agent service due to a library dependency issue, causing the agent device to go offline. This fix resolves the dependency handling during service restarts to ensure a smooth and reliable upgrade path for Linux endpoints.
Resolved an issue where SharePoint list view threshold limits caused backup task failures. The SharePoint backup module now gracefully handles SharePoint's list view threshold limit during backup execution. Instead of failing the entire backup task with an unhandled exception, the backup engine logs error code DV0395 specifying the affected site and list, allowing the job to continue backing up all remaining resources without interruption.
The events list now accurately displays log entries for restore tasks and other sub-logs. When a filter targets sub-logs exclusively, the system automatically switches to a dedicated query mode that retrieves sub-log entries independently from standard task package logs, delivering precise filter results without degrading database performance during standard event searches.
Resolved an issue where SharePoint backups failed when encountering a null Author field. The SharePoint backup module now correctly handles sites and items where the Author field contains a null value. Previously, encountering an unassigned Author field triggered a NullReferenceException, causing the backup task to fail. The backup engine now gracefully preserves null values during execution, ensuring uninterrupted backup operations across all SharePoint resources.
Fixed an issue where SLA percentages displayed incorrectly after switching Jira backup types. The SLA summary in the management panel now displays accurate data protection metrics, providing backup administrators with a clear and reliable view of overall coverage. Previously, switching a Jira backup plan configuration to granular backup mode could cause inaccurate SLA compliance percentages to render in the executive overview.
Temporary database files are now automatically removed from the target directory during Microsoft 365 email restore operations to on-premises locations. This eliminates leftover conversion containers that previously caused file access blocks during restoration and cluttered the final storage path.
Fixed an issue where refresh storage information tasks failed when target S3 storage was offline. The system now automatically skips the operation if target S3-compatible storage is unavailable at the completion of a replication task.
Resolved an issue where pre- and post-backup scripts failed on Linux agents due to system library interference. Pre-backup and post-backup scripts executed by the backup agent now run reliably when invoking applications that depend on system libraries. Previously, inherited agent environment settings interfered with external application execution, causing custom scripts to unexpectedly fail or crash.
The management panel now correctly displays descriptive, readable error messages instead of raw error codes when a SharePoint protection plan cannot be applied due to insufficient permissions or missing site assignments. This enables backup administrators to rapidly diagnose and resolve configuration issues directly within the interface without consulting external diagnostic documentation.
Fixed an issue where transient SMB errors caused backup and restore tasks to fail. Backup and restore operations targeting SMB storage destinations now gracefully handle transient STATUS_INVALID_SMB errors by automatically retrying the connection. Previously, temporary network or server-side interruptions could cause task execution to fail immediately. The engine now automatically recovers from connection drops, ensuring uninterrupted data protection and reliable recovery workflows.
Fixed an issue where Jira attachment backups failed with an OutOfMemoryException in large environments. These backups in large-scale organizations (500 GB+) now execute reliably without triggering memory exhaustion. This fix optimizes memory allocation during attachment processing, ensuring complete and reliable backups across all Jira space resources.
Resolved an issue where GitHub custom properties synchronization failed across all organizations due to single-organization transient errors. GitHub custom properties synchronization now continues processing remaining organizations if fetching the schema for one organization fails due to a transient error (such as HTTP 404). Previously, a transient error in a single organization blocked synchronization across the entire account; the system now preserves the existing schema for the affected organization while successfully updating all remaining entities. If a permanent authorization failure (HTTP 401) or suspended account state occurs, synchronization halts cleanly, and the organization is correctly flagged for repair.
Fixed an issue where backing up archived Confluence spaces triggered errors during blueprint and template processing. Backup operations for archived Confluence spaces now correctly capture space blueprints and templates across both full and incremental backup tasks. This update ensures complete, automated data protection for archived Confluence environments without requiring manual workarounds (such as temporarily restoring spaces to an active state).
Added support for SharePoint Online (cloud), enabling administrators to back up and restore SharePoint sites and associated files to Microsoft 365.
Added support for Confluence, enabling organizations to protect and recover spaces, pages, blog posts, attachments, and key metadata (including groups and templates). Connecting via personal access token (PAT) automatically provisions a default backup plan, enabling immediate protection with no additional setup. The solution supports flexible retention policies and per-user licensing to scale with the Atlassian environment. Granular restore capabilities allow recovery of individual spaces, pages, blog posts, as well as users and groups, reducing downtime and avoiding full-site restores.
Added support for Microsoft 365 shared mailboxes, enabling backup and restore with the same granularity as user mailboxes. Each shared mailbox requires a Microsoft user license. Existing organizations must be re-authorized to enable shared mailbox protection; newly added organizations include the required permissions by default.
Introduced support for GitHub sub-issues and custom issue types, allowing complex task hierarchies and tailored issue taxonomies to be fully preserved during backup and accurately reconstructed during restore. The feature is enabled by default for new backup plans and can be enabled for existing plans via toggle in the plan editor. Restores are supported to both original and alternative GitHub organizations, maintaining complete hierarchy integrity across all recovered items.
Added support for preserving original issue keys during Jira space-level (project-level) restores. Original keys are mapped to the GitProtect_Original Key custom field, enabling traceability across links, audits, and integrations. Available as an optional toggle in restore settings and compatible with existing metadata recovery options.
Introduced an organization-level mapping panel that eliminates the need for manual, repository-by-repository slug editing during restores. Administrators can redirect entire sets of repositories to target organizations, groups, or workspaces in a single step, including cross-platform restores between GitHub, GitLab, and Bitbucket. The feature is available for both cloud and self-hosted environments and includes validation to flag unavailable destinations before restore. Individual repository names can still be customized after mapping, ensuring flexibility while keeping the default workflow fast and scalable.
Implemented the ability to manually define the temporary data directory for backup agents (workers) in on-premises deployment models, using the TempFolder parameter in the configuration file.
Enhanced GitHub repository restores with cross-environment user identity preservation. A multi-layered matching strategy reconstructs team memberships, permissions, and issue ownership without manual intervention. When a match cannot be found, the restore operator is assigned as a placeholder, with the original identity clearly documented inline. A detailed post-restore summary highlights all unresolved mappings and affected resources, providing full transparency into any adjustments made during the restore process.
Extended backup and restore support to GitHub projects v2 for GitHub Enterprise Server, maintaining consistency and feature parity with GitHub cloud environments.
Changed the default restore behavior to use the most recent standalone repository backup instead of the repository copy included in project-level backups. This significantly reduces restore initialization time and improves overall recovery performance. The project-level restore setting remains available as an opt-in option, ensuring existing workflows remain unaffected.
Improved the manage accounts panel to eliminate ambiguity in credential troubleshooting. Additional Git accounts with expired or invalid credentials are now individually flagged with clear visual indicators, providing immediate insight into affected accounts. In addition, credentials are validated in real time during edits, ensuring misconfigurations are detected at the point of saving rather than during later backup failures.
Improved the GitLab comment backup process with a retry mechanism that prevents failures caused by premature response type errors.
Resolved an issue where restoring Microsoft 365 mailbox data to the original location with overwrite option enabled would fail with an "Access denied" error if the user account had been deleted and recreated using the same email address. Restores to recreated accounts now complete successfully without requiring workarounds such as disabling overwrite option or restoring to an alternate location.
Fixed an issue where Jira space (project) backups using partial name rules failed to include matching spaces. The backup engine now correctly processes wildcard characters, ensuring that all intended spaces are accurately identified and included in backups.
Fixed an issue where Jira workflows with custom transitions were not correctly restored to new instances. Workflows are now restored with full transition configuration intact.
Resolved an issue in Azure DevOps backups where deleted package versions in custom feeds could cause task failures. The backup engine now properly skips these versions, ensuring successful backup execution.
Errors encountered while downloading specific Azure DevOps package content no longer cause the entire backup task to fail.
Fixed an issue where restoring Jira issues from different space (project) types into a single new space could fail. Restores now complete successfully.
Jira assets custom fields are now correctly restored with their associated AQL filter configurations, including filter scope and work item scope.
Fixed a bug in Jira granular backup plans where editing and re-running a plan resulted in an incorrect start date (January 1, 1970) being shown in the aside panel. Backup execution timestamps now correctly reflect the actual start time.
Backup plans for GitHub cloud organizations using GitHub App authentication are now automatically restored and correctly reassigned after re-authentication, ensuring configurations remain intact even when the app is reinstalled. Previously, re-authentication would leave existing plans suspended and invalid, and editing those plans could create duplicates instead of updating the original.
Restoring Jira company-managed spaces (projects) now correctly preserves workflow transition rules that reference custom fields. Previously, certain rules—such as initial status transitions that copy field values from parent issues—could lose their field mappings during restore, which could prevent child issues from being created. This fix ensures workflow integrity is maintained for all protected company-managed spaces, even in complex rule configurations.
September 30
July 9
May 18
April 7
January 20
Updated the onboarding process for SaaS environments to simplify the initial setup, highlight key features of the solution (e.g., a custom encryption key), and guide users through the entire backup process.
Redesigned the GitProtect Management Service main dashboard. The improved dashboard provides the same information as before, along with a quick storage overview. The refreshed interface features a modern color palette and a cleaner, more visually appealing layout. This updated view helps users better understand the displayed data and quickly assess the overall status of environment protection at a glance.
Backup and recovery of repositories and metadata stored in GitHub Enterprise Cloud with data residency are now available.
Added support for AES-GCM (Advanced Encryption Standard – Galois/Counter Mode) encryption, a modern standard used in security protocols.
Extended the public API to support creation and management of Azure DevOps backup plans, consistent with other Git providers.
Added support for backing up and restoring related work links between Azure DevOps work items. During restore, these relationships are recreated wherever Azure DevOps allows, preserving work item context and navigation. If some links cannot be restored due to Azure DevOps limitations, the system reports which links were skipped and why, helping administrators quickly assess restore completeness.
Added an option in Jira granular backup plan settings to skip corrupted issue attachments during backup. Corrupted attachments are no longer treated as failed resources and do not affect the overall backup status. A warning in the backup summary indicates when attachments are corrupted.
Improved the Jira granular backup progress view so that processed elements are displayed under the current step instead of as a long list, consistent with other backup types.
The exact geographical location of Xopero Cloud Storage is now displayed in the location column of the storage list, providing administrators with information about data residency.
Docker container base images have been upgraded to Ubuntu 24.04 to ensure long-term support and improved security.
Improved the reliability of restoring Azure DevOps work items.
Added a warning message that is displayed when restoring an unsupported pipeline.
Added support for preserving the original tab name in recovered work items.
Backups of Jira spaces with restricted access now complete with a clear warning instead of an unhandled error.
During work item comment recovery, comments are created on behalf of a Jira user used for integration with GitProtect, making this user the author of all restored comments. With the updated Jira comment restore mechanism, each restored comment now includes information about its original author in its content.
Users can now exclude closed pull requests and issues from GitHub organization backup plans.
Improved handling of internal server errors during GitLab backups by adding additional retries for LFS uploads.
Added missing Microsoft 365 logs for events related to adding and removing tenants in GitProtect.
Improved logging for email message previews during Microsoft 365 restore operations. Event logs now clearly display the email subject, making it easier for administrators to identify which message was viewed.
Improved cleanup of incomplete deduplication backups by removing temporary invalid blocks, reducing storage usage and improving efficiency.
Added information about the agent (worker) to all backup summary types.
Resolved an issue where GitHub backup plans based on custom property rules could fail to start with specific rule configurations. The system now correctly validates and processes custom property-based selection rules, ensuring that repositories matching the configured criteria are consistently included and that the plan runs as expected.
Fixed an issue where GitHub releases created on a non-default branch could lose their latest status after restore. Restored repositories now retain the same latest release designation as the source repository.
Fixed an issue where GitHub issues restored to another organization could appear in a different order than in the original repository, affecting both closed and open issues. Restores now preserve the original issue order consistently, regardless of whether the organization is connected via OAuth or a personal access token, and regardless of whether the restore is performed from the DevOps view or from storage.
Fixed an issue where GitHub restores could display an incorrect number of failed items, especially for pull requests restored under limited token permissions. The restore process now correctly reports which GitHub resources were successfully recovered and which were not.
Fixed an issue where backup plans for Azure DevOps and GitHub ignored excluded repositories and still protected all repositories in the selected organization. Backup scope and the number of backup subtasks now correctly reflect only the repositories selected by the user, making backup configuration more predictable and easier to control.
When restoring GitLab repositories to GitHub, GitProtect now automatically shortens long merge request descriptions to comply with GitHub API limits.
Fixed an issue that prevented restoring Azure DevOps Server projects whose names contained a dot ('.'). Backups of such projects can now be fully restored without requiring additional name changes.
Fixed an issue where Azure DevOps projects using custom controls from the Microsoft Visual Studio Marketplace (such as the Multivalue control) were not fully restored from backup. After this change, if the original extension is installed in the target organization, restored work items correctly include all associated custom controls.
Fixed an issue where the last backup time for Jira spaces (projects) in the organization view was updated for all spaces after backing up a single Jira space. The last backup time is now displayed correctly for each space.
When configuring Jira granular backup plans by spaces (projects), deleted Jira spaces are no longer available for selection.
Fixed an issue where Jira organization metadata backup summaries showed incorrect counts of protected and restored items, including incorrectly counted directories.
Fixed an issue where some Jira issue attachments were missing from incremental backup restore points, despite being correctly captured in full backups.
When a Jira space backup encounters corrupted attachments, the backup summary now clearly displays a warning with details on which work items and how many attachments could not be protected.
Resolved an issue where Jira team-managed spaces' work items restored from backup could lose values in some custom and system fields. Work items restored from team-managed spaces now retain the same field data as the originals, improving data consistency and eliminating the need for manual corrections after a restore.
Data deletion tasks no longer remain stuck in the queued state after long-running backup jobs. Once running backups complete, queued deletion jobs now start and finish as expected, ensuring that backup plans and their data are removed in a timely and reliable manner.
Backups scheduled between 23:00 and 00:00 with an active backup window now start correctly according to the plan schedule. If a backup plan fails to start, the interface clearly informs the user of the failed execution, improving visibility for administrators when scheduled backups do not run.
The remote update of Linux agents (workers) has been improved so that the first update attempt now completes successfully instead of failing and requiring a manual retry.
Jira granular backup allows you to back up selected Jira spaces and specific elements within them, with the option to exclude particular issues using JQL, which streamlines the backup process and enhances flexibility in data protection. It works alongside disaster recovery backup, which is still available for Xopero ONE users.
Support for backing up and restoring a new type of Azure DevOps data: artifacts (including feeds and packages) has been added to Xopero ONE.
The protected data range for GitHub projects v2 has been extended to include backup and restore of draft issues, as well as additional fields such as status, labels, milestones, and user-defined fields.
GitHub repositories can now be automatically selected for backup based on custom properties defined by the user in GitHub.
Microsoft 365 groups are now visible in the user list and during backup plan configuration, making backup management and user selection more efficient.
It is now possible to exclude attachments from Jira disaster recovery backups.
The log detail level can now be configured using the environment variable XOPERO_LOG_LEVEL. This method is faster and more flexible than the previous approach, which required editing configuration files or creating new images in SaaS environments.
Ability to configure retry attempts for requests to the licensing server has been added.
GitProtect startup is now faster.
Increased the size and retention of log files for the Management Service and backup workers. Each file can now be up to 30 MB, and the system keeps up to 14 date-stamped files.
Security and efficiency in managing permissions and integration with external identity providers have been improved significantly.
Remote worker updates now have better error logging.
Management Service will now force password change upon first login.
The system now always requires full two-factor authentication (2FA), which means it can no longer be bypassed using a token stored in the browser. This safeguard provides additional protection against unauthorized access and ensures full session security.
Selection of the target project during restore to Azure DevOps has been improved.
Recovery of incremental Git repository backups and pull requests for GitHub Enterprise Cloud organizations has been optimized.
Error messages during the restoration of environments in GitLab are now clearer and easier to understand.
GitProtect now displays a warning when the number of available recovery codes is low. The warning appears when there is one or no recovery code remaining.
Fixed the issue where agent kept disconnecting during recovery of large GitHub repositories.
The notifications on Git organization dashboards now appear correctly and don't overlap.
Fixed an issue where restored GitHub Enterprise Cloud repositories would appear in incorrect order.
Resolved an issue that prevented changing the default worker when adding a new Jira organization to GitProtect.
Fixed an issue where an incorrect error message was displayed when registering a GitHub Enterprise Cloud account failed due to access-related problems.
Fixed an issue with restoring relationships between work items and objects in Jira disaster recovery.
Azure DevOps Wiki can now be backed up correctly, despite the project type.
Information about throttling and used credentials is now correctly displayed in task logs.
GitProtect now supports registering S3 storage in custom regions that were previously unsupported. This enables seamless use of such storage for backups and restorations, improving system flexibility and usability.
Improved how license restrictions are handled for storage in Management Service. Previously, these restrictions prevented creating replication plans from Xopero Cloud Storage to external providers like Wasabi. With this update, replication plans can now be created while respecting the applicable license limits.
Resolved an issue where the default worker information was not displayed for certain Xopero Cloud Storage repositories. Previously, this caused an orange warning indicating that no default worker was assigned.
Improved backup task resumption so that after an error, the task continues from the same backup type instead of automatically switching to incremental mode.
Improved the display of backup completion times on the dashboard. The COMPLETED column now shows the actual task completion time rather than the start time, providing a more accurate view of backup progress.
Added a clear message to inform non–primary administrator users that they cannot change login access from the MSP service.
Improved the display of device details for storage replication tasks, resolving the issue where worker information was missing in the management panel.
Introduced a mechanism that immediately displays information about missing Microsoft 365 licenses when adding additional organizations in GitProtect.
Fixed an issue where attachments in Microsoft 365 messages were not shown in the preview. Attachments are now correctly displayed when viewing messages in the GitProtect interface.
Added support for installing dependencies on openSUSE, with automatic detection of the Zypper package manager.
Fixed a bug that blocked licenses assigned to users of a deleted Microsoft 365 organization when an error occurred during application removal. Licenses are now correctly released, ensuring available licenses are not held unnecessarily.
Fixed an issue that caused backup agents to fail during installation or updates. With the new installer mechanism, all repairs and updates now complete smoothly.
Release 2.4.0, featuring FIPS-compliant encryption, Azure DevOps test plans backup, and Active Directory integration.
Added Active Directory LDAP integration featuring automated user provisioning upon login, group-to-role mapping, and administrative fallback authentication for high availability.
GitProtect.io & Active Directory Integration (LDAP) | User Management Automation
Introduced a new FIPS mode for backup plans using AES-CBC encryption. When enabled, the system ensures that encryption is performed exclusively via FIPS-validated modules on supported Windows backup agents, providing enhanced security compliance for regulated environments.
FIPS Compliant Encryption in GitProtect.io | Government-Grade Security
The GitProtect Management Service is now available in German. This localization covers all dashboard views, organization settings, and backup plan configurations, delivering a fully native user experience for the DACH region.
Added support for backup and recovery of Azure DevOps test plans and test suites. This includes preservation of test case relationships, configurations, and execution history, ensuring complete protection of the quality assurance lifecycle within DevOps projects.
Implemented detailed installer logging for Windows-based backup agent remote updates. Logs are now stored locally on the endpoint alongside standard agent logs, providing enhanced visibility into update failures and significantly simplifying troubleshooting.
Changed SharePoint site and template search functionality to be case-insensitive. Users can now find and select resources for backup using any combination of uppercase and lowercase letters, simplifying the search process.
Redesigned the repository exclusion mechanism in backup plans to improve clarity and control. Users can now efficiently manage which repositories are excluded from protection and receive immediate visual feedback on active exclusion rules.
Updated localization strings across the GitProtect Management Service panel to align with the latest official Atlassian terminology. This ensures a consistent user experience for customers operating GitProtect alongside Jira and Confluence, particularly regarding space and work item naming conventions.
Enhanced Azure DevOps integration stability by properly handling negative timeout values. Invalid timeout parameters received from the service provider are now ignored rather than causing task failures, ensuring uninterrupted backup processes.
GitProtect now automatically retries Jira API requests when encountering network-related errors (such as socket exceptions or connection resets). By default, the system performs up to five retry attempts using an exponential backoff strategy (1s, 2s, 4s, 8s, and 16s), which significantly improves the stability of backup and restore operations for large Jira instances or unstable network environments.
Enhanced the granularity and accuracy of error logs during the restoration of Jira work item types. If specific work item configurations cannot be fully restored due to target environment mismatches, the system now provides explicit, contextual details, allowing administrators to rapidly isolate and resolve data mapping issues.
Azure DevOps synchronization is now significantly faster, especially for environments with access to multiple organizations. This update eliminates past performance degradation, slashing synchronization times from up to 10 minutes down to approximately 10 seconds for standard Azure DevOps environments.
The system now correctly differentiates between standard Microsoft 365 users and shared mailboxes, ensuring that shared mailboxes are accurately identified and licensed during organization synchronization, eliminating the need to remove and re-add the organization to update mailbox statuses.
Resolved an issue where storage destinations without a defined capacity limit (unlimited) rendered incorrectly in the GitProtect Management Service dashboard. Previously, these were falsely displayed as 100% full with a low space badge; they now correctly display an infinity symbol (∞) and no longer trigger misleading low-space warnings.
The predefined backup plan modal dialog no longer incorrectly displays onboarding steps when adding subsequent organizations. The onboarding progress bar is now strictly reserved for the initial setup, ensuring a cleaner, distraction-free interface for experienced users.
The last backup task summary chart now features an auto-scaling, dynamic Y-axis. Previously constrained to a fixed range of 0–280, the chart now automatically scales based on the highest data point, ensuring that large-scale datasets are never visually clipped and low values remain highly readable.
Fixed a bug where assigning a backup agent to a backup plan triggered the automatic creation of folders across all local storage destinations. Directories are now created strictly on-demand when a storage destination is actively utilized by a task, preventing the accumulation of empty folders across the file system.
Fixed an issue where Git LFS (Large File Storage) objects with .txt and .html extensions were not being correctly secured. The system now properly identifies and backs up these specific file types within the LFS framework, ensuring complete repository data integrity.
Resolved an issue with GitHub App integration, where repositories were automatically disconnected upon encountering transient authorization errors. The system now safely maintains the repository connection and automatically retries the synchronization, eliminating the need for manual administrative intervention.
Fixed an issue where custom field values within Jira work items were not correctly restored. All metadata associated with custom fields is now accurately preserved during the restoration process.
Resolved an issue where archived Confluence spaces were restored as active spaces and missing critical components such as folders, smart links, boards, and databases. Archived status and all associated content types are now correctly preserved during recovery.
Fixed an issue where Jira active spaces which were previously marked as deleted or archived were not restored to an active state, even if they had been reactivated in Jira before the last backup. The system now correctly synchronizes and restores active status for all spaces.
GitHub repository restoration now correctly handles environments with a high volume of branches (exceeding 500). This update resolves a "Bad request" error that previously occurred during incremental restoration for complex repository structures, ensuring reliable recovery regardless of branch count or backup type.
Jira restoration now correctly preserves custom screens associated with workflow transitions. When a space is recovered or migrated to a new instance, transitions configured to show a screen accurately maintain their original screen associations, provided the target screens are part of the space's screen scheme.
Jira restoration now correctly preserves field mapping rules within workflow transitions, including configurations that copy custom field values from parent work items. This fix ensures that restored workflows maintain their original operational logic, enabling seamless creation and recovery of sub-tasks that depend on these transition behaviors.
Jira backup plans now correctly process JQL exclusion rules based on creation date, modification date, and specific field values. This update ensures work items are accurately filtered according to the defined criteria and resolves an issue where work items with empty field values were unintentionally excluded when using certain JQL operators.
Confluence restoration now correctly preserves statuses assigned to draft pages and blog posts. All draft content in the restored space retains its original workflow status, ensuring consistency between the source and restored environments.