Skip to main content

Agility Sync Point Release Notes

This page contains the release notes for all Agility Sync point releases.

For Agility Sync point releases that are currently supported, see the Digital.ai Agility point release notes.

Agility Sync Point Release 24.3.4​

Agility Sync 24.3.3 brings you the following new features and bug fixes.

Bug Fixes​

  • Removed unwanted check for sub-task mapping activation.

Agility Sync Point Release 24.3.3​

Agility Sync 24.3.3 brings you the following new features and bug fixes.

Bug Fixes​

  • In multi-mapping setups, sync incorrectly picked up Migrate Create events even when only Update & Delete was selected. This has been fixed to respect the configured event types

Agility Sync Point Release 24.3.2​

Agility Sync 24.3.2 brings you the following new features and bug fixes.

Bug Fixes​

  • Resolved an issue where clicking on the Else If section under Tasks triggered an unexpected alert or error message.

Agility Sync Point Release 24.3.1​

Agility Sync 24.3.1 brings you the following new features and bug fixes.

Bug Fixes​

  • Editing mappings in a dropdown field no longer triggers the error "value has been modified" when multiple values have different display names but share the same internal ID/Value.
  • The relationship for skipped events is now correctly set to the assigned work item instead of the default one.
  • AgilitySync no longer creates duplicate Create Events when adding children and performing updates on them.
  • The Value Area field in Azure DevOps (ADO) is now correctly recognized, allowing proper value mapping in AgilitySync.
  • One-to-many mappings between Agility and Azure now sync work items correctly across all mappings, preventing webhook events from skipping valid syncs.
  • Team values now sync correctly during migration.
  • Certain Test Asset fields have been removed from the hidden state in Agility.

Agility Sync Point Release 24.2.3.0​

Agility Sync 24.2.3.0 brings you the following new features and bug fixes.

Bug Fixes​

  • Sync Selected Event type is picking migrate create events even if only update & delete option is selected and configured.

Agility Sync Point Release 24.2.2.0​

Agility Sync 24.2.2.0 brings you the following new features and bug fixes.

Bug Fixes​

  • Resolved an issue where creating a dependency in Jira failed with the following error No issue link type with name block found.
  • Fixed an issue causing attachment sync failures with the error Attachment sync failed. Unable to create outbound attachment object. Error is [inbound]and prevented duplicate attachments during re-sync.
  • Addressed an error where description updates from Agility for existing work items triggered a field_name error after embedding images.
  • Corrected an issue where the wrong webhook handler was being triggered, leading to incorrect updates.

Agility Sync Point Release 24.2.1.0​

Agility Sync 24.2.1.0 brings you the following new features and bug fixes.

Bug Fixes​

  • Fix for embed image sync issue when description and other html fields are mapped.

Agility Sync Point Release 24.1.3.0​

Agility Sync 24.1.3.0 brings you the following new features and bug fixes.

Bug Fixes​

  • Fix for task related performance issue.

Agility Sync Point Release 24.1.2.0​

Agility Sync 24.1.2.0 brings you the following new features and bug fixes.

Bug Fixes​

  • Fix for issue in retrieving Epic fields from Agility.

Agility Sync Point Release 24.1.1.0​

Agility Sync 24.1.1.0 brings you the following new features and bug fixes.

Bug Fixes​

  • Edit mapping resulted in 501 Gateway error, this issue is fixed.

Agility Sync Point Release 23.3.0.0.87​

Agility Sync 23.3.0.0.87 brings you the following new features and bug fixes.

Bug Fixes​

  • Fixed webhooks Duplicate key issue while doing bulk updates of workitems.

Agility Sync Point Release 23.3.0.0.85​

Agility Sync 23.3.0.0.85 brings you the following new features and bug fixes.

Bug Fixes​

  • JQuery User Interface library upgraded to address security issues
  • Fixed migrate create for request asset in Agility.

Agility Sync Point Release 23.3.0.0.84​

Agility Sync 23.3.0.0.84 brings you the following new features and bug fixes.

Bug Fixes​

  • Rest API updates after JIRA Cloud API changes mapping.
  • Support Project asset for ServiceNow.
  • Duplicates being created when update event pops in before create event.
  • Embed Image sync when permission is not available to view image.

Agility Sync Point Release 22.0.1​

Agility Sync 22.0.1 brings you the following new features and bug fixes.

New Features​

  • Sync Specific condition now supports syncing updates to workitems
    You can now use Sync Specific conditions to sync updates made to workitem fields.
    If multiple mappings exist for a project, updates are synced only via the mapping used to sync the workitem and skipped for other mappings to avoid duplication.

For more information, see Sync Specific Workitem.

Bug Fixes​

  • Fixed issue with to sync failing when relationship status was changed in the mapping.
  • Fixed issue that caused parent and child workitems created using migrate create on to not sync with .
  • Fixed issue that caused duplicate updates when multiple mappings are created with the same project in or to different projects in .
  • Fixed issue that caused the "UnboundLocalError: local variable 'dep_issue_info' referenced before assignment" error while adding a parent link in workitem sync, with Dependencies Enabled and Relationships disabled.
  • Fixed issue that caused Create workitem with tags to fail from to .
  • Fixed issues with to ALM QC sync.
  • Added the '--' value to the Team field in Agility Sync to be mapped with the 'Unassigned' value in .
  • Fixed mapping issue that caused Boolean fields to be displayed as TEXT in the field mapping page and caused the sync to fail.
  • Fixed the ['NoneType' object has no attribute 'split'] error caused by empty fields during migrate-create.
  • Fixed the "Unable to normalize fields. Error is [u'name']" error caused when workitems contained a hyperlink.
  • Fixed issue that caused the sync to fail or showed incorrect value when the sprint field was updated multiple times.
  • Default value assigned to a field can now be deleted from the value mapping section.

Agility Sync Point Release 21.3.1​

Agility Sync 21.3.1 brings you the following new features and bug fixes.

New Features​

  • Sync issues with Ranking enabled (--- integration)

    You can now create mappings to sync ranked issues with with the ranking order preserved in .

    This feature comes in handy when you migrate your issues to (and not vice versa) and want to preserve the ranking order in .

    Select the Migrate with Ranking order check box when you create a mapping to have your ranked issues synced in the same order in .

  • Sync the Linked Issues field in to the Portfolio Item Field in

    The Relationships function has been extended to sync the Linked Issues field in to the Portfolio Item field in . The use case is to sync the Linked Issued field of type "Parent of" with the Portfolio Item field in .

Bug Fixes​

  • Data migration from to in a given data range fetches work item updates exactly in the given date range ignoring the fact that latest updates to the work item (done after the end date) are available.
  • Migrating Stories from to was failing
  • Relationships doesn't work with Feature Request to Request with Epic as parent
  • Data sync fails with --- integration when you user names are used in comments

Agility Sync Point Release 21.2.1​

Overview​

Here's a list of new features and bug fixes in Agility Sync 21.2.1.

Support for Delete event​

In addition to CREATE and UPDATE events, Agility Sync now supports DELETE event. When you delete a work item in one of the integrated tools, the corresponding work item is deleted in the tool at the other end of the integration.

What happens when you Undelete work items in ? ( --- mapping)

While a work item---if deleted---is deleted forever in , you can undelete a deleted work item in at a later point in time. In this case, a new work item is created in when you undelete a deleted work item in .

Mapping Planning Folders with Agility Planning Levels

The use case is to map the Planning Folders with Planning Levels---at a field mapping level---so that you can have the mapped Planning Folder and Planning Level always in sync. Work items created, updated, or deleted in a Planning Folder are synced with the mapped Planning Level.

You can also have conditional syncing (Sync Specific Work Item) based on specific Planning Folders and Planning Levels

Filters in View Logs page​

The View Logs page is now equipped with filters to let you filter the list of log entries. You can filter the list by the following fields:

  • Source ID---Type the source ID and click the filter icon (or press enter)
  • Destination ID---Type the destination ID and click the filter icon (or press enter)
  • Event Type---Select the type of event from the drop-down list and click the filter icon (or press enter)
  • Status---Select the status from the drop-down list and click the filter icon (or press enter)

Created By and Updated By Columns in Mapping List page​

The Mapping List page now shows the user that created or updated a mapping. The Created By and Updated By columns in the Mapping List page show the user name of the user that created and updated the mapping respectively.

Ability to view Event Info (JSON payload)​

You can now click the Event Info icon of any event (on the View Logs page) to view the JSON payload for that event.

Rich-text formatting support for Text fields​

now supports syncing text fields with rich text formatting. Rich text-formatted content is now synced without losing the formatting done in the source system.

Bug Fixes​

  • The account ID of the user shows up in the Comments section of the work item (instead of showing the user name) when you use @mentions in Conversations.

Agility Sync Point Release 21.1.1​

Overview​

Here is the list of new features and bug fixes in Agility Sync 21.1.1.

  • You can now create mappings to sync Iterations and Sprints. Iterations and Sprints are assets supported by Agility Sync. The use case here is to create a mapping to sync Agility Iterations with Sprints as and when you create or update Iterations or Sprints. For more information, see Create Mapping to Sync Iterations and Sprints.
  • Value Mapping Settings---You may or may not have mapped all of the values in single-select drop-down lists. In such cases, the sync operation may fail as Agility Sync cannot figure out what to do when a single-select drop-down field is updated with an unmapped value. You can use the Value Mapping Settings to resolve such conflict situations arising out of unmapped values. For more information, see Value Mapping Settings.
  • When and label fields are mapped, any updates to labels, by default, would overwrite the full list of labels instead of appending new labels to the already existing list of labels. However, you can choose to either overwrite or append via customizations. Use the customization script for planning level to label and add the following line to have the labels appended: Planning Level to Label Overwrite=False.
  • You can now have changes to certain fields of interest posted to the Comments and Conversations sections of and respectively.

For example, the following image shows a handful of and fields---whose values---if updated---are posted to the Comments and Conversations sections of and respectively.

The use case here is to keep tabs on changes to unmapped fields and other fields of interest.

For example, the following image shows a list of fields---with values---that are updated in and hence are posted to workitem's Conversations as configured.

  • Clicking a mapping from the Mappings List page opens up the mapping in a new tab.
  • In addition to the Mappings List page, the View Logs link is now available on the View/Configure Mapping pages.
  • Users with the Shared Asset Manager role can now view the log files for Agility Sync mappings and Webhooks.
  • Sync Reference is now enabled for --- integration. However, you must create the ID and URL custom fields and map them with 's ID and URL fields (when you create an --- mapping) to have the backlinks synced between and .
  • A fully qualified workitem URL (with the target system's domain name) is returned post sync by the target system when a new workitem is created in .
  • Performance improvements to make Agility Sync pages load faster than before.