Skip to main content
System StatusContact Support

Documentation related to the following products will soon be moved to a new portal: ( Agility, Agility Connect and Agility Integrations Continuum and ALM Connect
Links from the site will automatically redirect to the new site.
If you have any questions, please contact Support. Agility Community

Agility Connect Point Release 21.3.1

New Home for Agility Connect Documentation 

Edit section

See for the most recently updated Agility Connect documentation. This space will be decommissioned shortly. 

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

New Features

  • Sync Jira issues with Ranking enabled (AgilityJira integration)

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

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

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


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

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


    For more information, see Syncing the Linked Issues field in Jira to the Portfolio Item Field in Agility.


Bug Fixes

  • [Data MIgration] Data migration from Jira to Agility 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.
  • [Data Migration] Migrating Jira Stories from Jira to Agility was failing
  • [Data Migration] Relationships doesn't work with Feature Request to Request with Epic as parent
  • [Data Migration] Data sync fails with Jira—Agility integration when you user names are used in Jira comments