• Extended email bulk mapping functionality - previously the functionality was case sensitive, now is case insensitive. Users should be able to map email addresses no matter how they are written (john.smith@test.com ↔︎ John.Smith@test.com).

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Extended email bulk mapping functionality - previously the functionality was case sensitive, now is case insensitive. Users should be able to map email addresses no matter how they are written (john.smith@test.com ↔︎ John.Smith@test.com).

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Extended email bulk mapping functionality - previously the functionality was case sensitive, now is case insensitive. Users should be able to map email addresses no matter how they are written (john.smith@test.com ↔︎ John.Smith@test.com).

Make sure to also run the latest version of TFS4JIRA Synchronizer.

We have added Jira Cloud REST API support to handle the ability to correctly predict different behaviors to support the synchronization of issues without parent.

We have fixed an issue preventing hierarchy synchronization while running initial synchronization in modes #3 and #4

Make sure to also run the latest version of TFS4JIRA Synchronizer.

We have added Jira Cloud REST API support to handle the ability to correctly predict different behaviors to support the synchronization of issues without parent.

We have fixed an issue preventing hierarchy synchronization while running initial synchronization in modes #3 and #4

Make sure to also run the latest version of TFS4JIRA Synchronizer.

We have timely corrected the new Jira API behavior for build 10.1.1. However, Atlassian has since rolled back the change as identified here https://developer.status.atlassian.com/incidents/6hy7qgxmc1pz. We have taken additional action and ask that customers who have installed the version 10.1.1 to please rollback to TFS4JIRA Synchronizer build 10.1.0.

Appfire has since recalled TFS4JIRA Synchronizer build 10.1.1.

We have timely corrected the new Jira API behavior for build 10.1.1. However, Atlassian has since rolled back the change as identified here https://developer.status.atlassian.com/incidents/6hy7qgxmc1pz. We have taken additional action and ask that customers who have installed the version 10.1.1 to please rollback to TFS4JIRA Synchronizer build 10.1.0.

Appfire has since recalled TFS4JIRA Synchronizer build 10.1.1.

• API for check-ins configuration management
• Updated jQuery library and other security fixes
• Improved check-ins performance
• Added an option to scan for check-ins based on committed date
• Vertical line in rich text customizations

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• API for check-ins configuration management
• Updated jQuery library and other security fixes
• Improved check-ins performance
• Added an option to scan for check-ins based on committed date
• Vertical line in rich text customizations

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• TFS4JIRA Self-hosted now supports in place profile migration to point to Jira Cloud - see TFS4JIRA - Server to Cloud Migration
• Improved handling of HTML tag in issue description and comments
• Fixed bug with commits not showing in case of identical hashes for two repos

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• TFS4JIRA Self-hosted now supports in place profile migration to point to Jira Cloud - see TFS4JIRA - Server to Cloud Migration
• Improved handling of HTML tag in issue description and comments
• Fixed bug with commits not showing in case of identical hashes for two repos

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Improved how filters handle cache
• Added control to verify whether filter is enabled
• Fixed issues with unsupported “Request language” fields in Jira Service Projects.
• Fixed problems with converting List in Jira
• Fixed issue with bulk password editing directly in database
• Security improvements

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Improved how filters handle cache
• Added control to verify whether filter is enabled
• Fixed issues with unsupported “Request language” fields in Jira Service Projects.
• Fixed problems with converting List in Jira
• Fixed issue with bulk password editing directly in database
• Security improvements

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Added support of base64 encoded images
• Synchronization speed performance improvements - do not load sprints if they are not mapped, share cache between profiles within the same Jira project
• Improved transformation of old TFS filters into WIQL
• Fixed status multi-mapping in profile API

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Added support of base64 encoded images
• Synchronization speed performance improvements - do not load sprints if they are not mapped, share cache between profiles within the same Jira project
• Improved transformation of old TFS filters into WIQL
• Fixed status multi-mapping in profile API

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Maximized synchronization control with WIQL and JQL to save time when fetching only relevant items
• Added the ability to map all Jira users, in addition to project assignable users
• Test management work items types in ADO can now be deleted during initial synchronization
• Made scanning multiple Git repos faster and easier. Inaccessible repos will be ignored while accessible repos continue to be scanned
• And of course many security fixes

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Maximized synchronization control with WIQL and JQL to save time when fetching only relevant items
• Added the ability to map all Jira users, in addition to project assignable users
• Test management work items types in ADO can now be deleted during initial synchronization
• Made scanning multiple Git repos faster and easier. Inaccessible repos will be ignored while accessible repos continue to be scanned
• And of course many security fixes

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• TFS custom identity field is now treated as user field
• Embedded images synchronization for Jira Cloud - replacement of existing attachments endpoint due to deprecation
• Added endpoint to fetch all profiles ids
• Security fixes

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• TFS custom identity field is now treated as user field
• Embedded images synchronization for Jira Cloud - replacement of existing attachments endpoint due to deprecation
• Added endpoint to fetch all profiles ids
• Security fixes

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Added compatibility with SQL Express. For more details how to migrate from SQL CE, please check the following page: How to migrate SQLCE to SQL Express

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Added compatibility with SQL Express. For more details how to migrate from SQL CE, please check the following page: How to migrate SQLCE to SQL Express

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Added support for “all” Git repositories configuration
• Introduced the truncation of too long rich text field on Jira side
• Security fixes

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Added support for “all” Git repositories configuration
• Introduced the truncation of too long rich text field on Jira side
• Security fixes

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Fixed users bulk mapping issue for Jira DC.
• Verified support of Azure DevOps 2022

Make sure to also run the latest version of TFS4JIRA Synchronizer

• Fixed users bulk mapping issue for Jira DC.
• Verified support of Azure DevOps 2022

Make sure to also run the latest version of TFS4JIRA Synchronizer

• Added support for Jira 9.3
• Added user mapping search view box for faster mapping process
• Jira Datacenter or Server version 8.20.7 with over 1000 users - fixed issue related to the ability to load all users
• Improved and fixed the sorting mechanism for initial synchronization when working with hierarchy and subtasks
• Improved synchronization of rich texts fields with pre tag.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Added support for Jira 9.3
• Added user mapping search view box for faster mapping process
• Jira Datacenter or Server version 8.20.7 with over 1000 users - fixed issue related to the ability to load all users
• Improved and fixed the sorting mechanism for initial synchronization when working with hierarchy and subtasks
• Improved synchronization of rich texts fields with pre tag.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

We've fixed problem for checkins panel not always properly loaded for Jira 9.0 and newer.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

We've fixed problem for checkins panel not always properly loaded for Jira 9.0 and newer.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Spartez has joined the Appfire family, and we are bringing all our apps together under a single brand. We have updated The TFS4JIRA logo to reflect this initiative and will continue enhancing your Appfire experience.
• Better handling ResolvedReason and Reason in Azure DevOps/TFS different model processes
• Fixed REST API for profile management not setting Resolution field mapping
• Configurable project collection of users for TFS
• Hierarchy synchronization is now working even if issue has attachment
• Security fixes

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Spartez has joined the Appfire family, and we are bringing all our apps together under a single brand. We have updated The TFS4JIRA logo to reflect this initiative and will continue enhancing your Appfire experience.
• Better handling ResolvedReason and Reason in Azure DevOps/TFS different model processes
• Fixed REST API for profile management not setting Resolution field mapping
• Configurable project collection of users for TFS
• Hierarchy synchronization is now working even if issue has attachment
• Security fixes

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Functional features:

• Get ready for Jira 9 - we are compatible with Jira 9 EAP03
• Automate profile creation and management with new REST API, enjoy Swagger UI that is available on profile list page

Performance and Security:

• Handle bigger projects and bigger data sets, memory allocated to caches is increased thanks to new x64 architecture
• Measure performance of synchronization and identify bottlenecks with structured performance data available via ETW
• Stay secure - 3d party libraries with security vulnerabilities have been upgraded

Bugfixes:

• Added support for “Does not contain” Azure Filter - now it can be transformed to WIQL
• Improved precision of handling start and end dates for initial synchronization from Azure to Jira

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Functional features:

• Get ready for Jira 9 - we are compatible with Jira 9 EAP03
• Automate profile creation and management with new REST API, enjoy Swagger UI that is available on profile list page

Performance and Security:

• Handle bigger projects and bigger data sets, memory allocated to caches is increased thanks to new x64 architecture
• Measure performance of synchronization and identify bottlenecks with structured performance data available via ETW
• Stay secure - 3d party libraries with security vulnerabilities have been upgraded

Bugfixes:

• Added support for “Does not contain” Azure Filter - now it can be transformed to WIQL
• Improved precision of handling start and end dates for initial synchronization from Azure to Jira

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Performance:

• Decreased latency and network traffic for profiles with filters

Bugfixes:

• TFS 2018 embedded images in HTML now correctly synchronising to Jira
• Attachment names are now allowed to contain special characters
• Removing a label in Jira will correctly remove the tag in TFS
• Hyperlinks with space and removal of hyperlinks synced accordingly
• Rich text fields with empty line(s) in lists correctly being synced
• Duplicated TFS usernames available and visible in user mapping

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Performance:

• Decreased latency and network traffic for profiles with filters

Bugfixes:

• TFS 2018 embedded images in HTML now correctly synchronising to Jira
• Attachment names are now allowed to contain special characters
• Removing a label in Jira will correctly remove the tag in TFS
• Hyperlinks with space and removal of hyperlinks synced accordingly
• Rich text fields with empty line(s) in lists correctly being synced
• Duplicated TFS usernames available and visible in user mapping

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Performance:

• Reduced amount of network calls to Azure DevOps API by introducing configurable cache for “Get Work Item Type” endpoint.

Bugfixes:

• Synchronization of very long comments no longer fails. Instead, an excerpt is synchronized, together with a link to the original
• Synchronization of links with long urls from Jira to Azure DevOps/TFS now works flawlessly.
• User mapping page will load correctly when there are multiple project collections in TFS.
• State transition synchronization from Azure DevOps/TFS to Jira works properly when states are multi-mapped.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Performance:

• Reduced amount of network calls to Azure DevOps API by introducing configurable cache for “Get Work Item Type” endpoint.

Bugfixes:

• Synchronization of very long comments no longer fails. Instead, an excerpt is synchronized, together with a link to the original
• Synchronization of links with long urls from Jira to Azure DevOps/TFS now works flawlessly.
• User mapping page will load correctly when there are multiple project collections in TFS.
• State transition synchronization from Azure DevOps/TFS to Jira works properly when states are multi-mapped.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Fixed:
  • A display of custom field configured to keep the synchronization status (previously a wrong field was shown in case of multiple custom fields available);
  • Fetching of repositories configuration from Azure/TFS on-premises instance if the user account is managed through ActiveDirectory;
  • Links synchronization in case if a linked item is unavailable or doesn’t contain a required custom field;
• Added a possibility to configure items synchronization order in web.config file, based on issue/item type, this is a workaround for a hierarchy structure synchronization that is not fully supported by Synchronizer yet.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

• Fixed:
  • A display of custom field configured to keep the synchronization status (previously a wrong field was shown in case of multiple custom fields available);
  • Fetching of repositories configuration from Azure/TFS on-premises instance if the user account is managed through ActiveDirectory;
  • Links synchronization in case if a linked item is unavailable or doesn’t contain a required custom field;
• Added a possibility to configure items synchronization order in web.config file, based on issue/item type, this is a workaround for a hierarchy structure synchronization that is not fully supported by Synchronizer yet.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Features:

Added synchronization of:

• Embedded images in comments and description fields
• Nested bullet and numbered lists

Bugfixes:

• Enabled editing of links mapping when a mapped link type was removed in Jira
• Improved fetching of large numbers of sprints
• Optimized synchronization of TFS revisions (to fix “out of memory” issues)
• Speeded up loading of check-ins panel and fixed display of the expired license information in it

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Features:

Added synchronization of:

• Embedded images in comments and description fields
• Nested bullet and numbered lists

Bugfixes:

• Enabled editing of links mapping when a mapped link type was removed in Jira
• Improved fetching of large numbers of sprints
• Optimized synchronization of TFS revisions (to fix “out of memory” issues)
• Speeded up loading of check-ins panel and fixed display of the expired license information in it

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Security enhancements:

• Administrator operations have been secured with the additional privileges check.
• Disabled a possibility to scan Spartez Software network through TFS4JIRA configuration page for Jira Cloud.

Bugfixes:

• Attachments are not re-created after being removed from Jira or Azure DevOps/TFS.
• Newly added links are synchronized within a single synchronization cycle.
• Fixed synchronization failures for next-gen JSD projects.
• Fixed PBI ↔︎ Story synchronization when parent item is marked as -skip-.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Security enhancements:

• Administrator operations have been secured with the additional privileges check.
• Disabled a possibility to scan Spartez Software network through TFS4JIRA configuration page for Jira Cloud.

Bugfixes:

• Attachments are not re-created after being removed from Jira or Azure DevOps/TFS.
• Newly added links are synchronized within a single synchronization cycle.
• Fixed synchronization failures for next-gen JSD projects.
• Fixed PBI ↔︎ Story synchronization when parent item is marked as -skip-.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Security enhancement:

• Switched to the official library supported by Atlassian for communication with Jira Cloud

Features:

• Initial synchronization error limit is now customizable through web.config file

Bugfixes:

• Avoid unnecessary text formatting updates for the fields that were not modified

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Security enhancement:

• Switched to the official library supported by Atlassian for communication with Jira Cloud

Features:

• Initial synchronization error limit is now customizable through web.config file

Bugfixes:

• Avoid unnecessary text formatting updates for the fields that were not modified

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Features:

• Enabled users to correct mappings for the fields that were removed or hidden in Jira / TFS from UI
• Added sub-navigation to fields mapping and de-cluttered UI

Bugfixes:

• Fixed intermittent errors related to SQL connector exceptions (SqlCeConnection) resulting in synchronization failures
• Fixed Jira filters when search was referencing “empty” values
• Fixed synchronization issue for Jira instances with “/jira” path in URL

Make sure you run the latest version of TFS4JIRA Synchronizer.

Features:

• Enabled users to correct mappings for the fields that were removed or hidden in Jira / TFS from UI
• Added sub-navigation to fields mapping and de-cluttered UI

Bugfixes:

• Fixed intermittent errors related to SQL connector exceptions (SqlCeConnection) resulting in synchronization failures
• Fixed Jira filters when search was referencing “empty” values
• Fixed synchronization issue for Jira instances with “/jira” path in URL

Make sure you run the latest version of TFS4JIRA Synchronizer.

TFS4JIRA now supports Jira's Next-gen projects - we made configuration easier by showing relevant fields only and adding support of next-gen specific fields - please check details below.

Features:

Hierarchy synchronization

You can now synchronize and maintain project hierarchy levels (Epic - Story/Task - Sub-task) between Jira Next-Gen project and Azure DevOps project using Parent/Child relation.

Sprints synchronization

Sprints ↔︎ Iteration Path synchronization for Next-Gen projects works the same as for Classic projects. Likewise, three mapping modes are available:

• Copy full Azure DevOps tree path
• Copy last part of Azure DevOps tree path
• Map values

Bugfixes:

• Improved synchronization of images in comments for Azure DevOps Server
• Misconfigured boards caused synchronization failures
• Synchronization failures when Synchronizer had no permissions to access linked work items

Upgrade following the link: TFS4JIRA Synchronizer.

TFS4JIRA now supports Jira's Next-gen projects - we made configuration easier by showing relevant fields only and adding support of next-gen specific fields - please check details below.

Features:

Hierarchy synchronization

You can now synchronize and maintain project hierarchy levels (Epic - Story/Task - Sub-task) between Jira Next-Gen project and Azure DevOps project using Parent/Child relation.

Sprints synchronization

Sprints ↔︎ Iteration Path synchronization for Next-Gen projects works the same as for Classic projects. Likewise, three mapping modes are available:

• Copy full Azure DevOps tree path
• Copy last part of Azure DevOps tree path
• Map values

Bugfixes:

• Improved synchronization of images in comments for Azure DevOps Server
• Misconfigured boards caused synchronization failures
• Synchronization failures when Synchronizer had no permissions to access linked work items

Upgrade following the link: TFS4JIRA Synchronizer.

Features:

• Sprint synchronization support for Next-Gen projects

Bugfixes:

• optimized memory usage to enable long running uninterrupted service;
• Jira filters support Fix Version/s, Affects Version/s, Components and cascading select fields;
• IterationPath and AreaPath synchronization supports empty value;
• synchronization doesn't take into account unsupported fields, if they were not mapped;
• solved problem with duplicated Jira Issue types and statuses;
• improved synchronization of attachments from DevOps Azure to Jira;
• transition is now possible for work items with more than 200 entries in history.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Features:

• Sprint synchronization support for Next-Gen projects

Bugfixes:

• optimized memory usage to enable long running uninterrupted service;
• Jira filters support Fix Version/s, Affects Version/s, Components and cascading select fields;
• IterationPath and AreaPath synchronization supports empty value;
• synchronization doesn't take into account unsupported fields, if they were not mapped;
• solved problem with duplicated Jira Issue types and statuses;
• improved synchronization of attachments from DevOps Azure to Jira;
• transition is now possible for work items with more than 200 entries in history.

Make sure to also run the latest version of TFS4JIRA Synchronizer.

Performance:

• synchronization of a single item is now 10 to 40% faster (depending on configuration)
• improved initial synchronization from Azure DevOps Services to Jira - it can be even twice faster for a large number of issues synchronized (1000+).

Features:

• added support of a special mode for initial synchronization that can be used to synchronize items from the same project in a source system to a different project in a target system
• enabled user mapping for TFS instances with 10k+ users

Bugfixes:

• made interruption of initial synchronization more responsive
• removed duplicating "Resolution" field and kept only the one that we actually support
• added extra logging around attachments synchronization for easier troubleshooting

Performance:

• synchronization of a single item is now 10 to 40% faster (depending on configuration)
• improved initial synchronization from Azure DevOps Services to Jira - it can be even twice faster for a large number of issues synchronized (1000+).

Features:

• added support of a special mode for initial synchronization that can be used to synchronize items from the same project in a source system to a different project in a target system
• enabled user mapping for TFS instances with 10k+ users

Bugfixes:

• made interruption of initial synchronization more responsive
• removed duplicating "Resolution" field and kept only the one that we actually support
• added extra logging around attachments synchronization for easier troubleshooting

Added JQL support for Jira custom fields

Added JQL support for Jira custom fields

• We've updated .NET framework to version 4.8
• Added new colors to logs view for better readability
• Added alphabetic sorting to user mapping list
• Added original comment timestamp to issue/item comment after synchronization
• Added WIQL query visibility into the logs view
• Optimized network performance - added issue filtering while requesting data from JiraPlease note that current profiles' Jira filters will be transformed to JQL, for more info see the documentation.
• Added missing information to logs view
• We've fixed an increased amount of user sessions generated by synchronizer after upgrade to 7.8.x
• We've fixed comments syncing and duplicates
• General stability and performance improvements

• We've updated .NET framework to version 4.8
• Added new colors to logs view for better readability
• Added alphabetic sorting to user mapping list
• Added original comment timestamp to issue/item comment after synchronization
• Added WIQL query visibility into the logs view
• Optimized network performance - added issue filtering while requesting data from JiraPlease note that current profiles' Jira filters will be transformed to JQL, for more info see the documentation.
• Added missing information to logs view
• We've fixed an increased amount of user sessions generated by synchronizer after upgrade to 7.8.x
• We've fixed comments syncing and duplicates
• General stability and performance improvements

Fixed problem synchronizing comments from Jira Cloud to Azure after Jira Cloud API change

Fixed problem synchronizing comments from Jira Cloud to Azure after Jira Cloud API change

Fix for bug:

• Jira <- Azure DevOps sync field one way direction is being ignored if configured in other fields two-side direction

Fix for bug:

• Jira <- Azure DevOps sync field one way direction is being ignored if configured in other fields two-side direction

Fixes for bugs:

• Synchronizer fails to synchronize if it encounters attachment with forbidden for file signs on Windows or Jira system
• Failing to synchronize if encountering attachment in issue that was removed in Jira server but link was still present
• Failing to synchronize if encountering attachment with 0 size on Azure DevOps side
• Missing users that are not in Windows Live ID domain in Azure DevOps
• Failing for sync few field types and if default on Azure DevOps side is set to null

Fixes for bugs:

• Synchronizer fails to synchronize if it encounters attachment with forbidden for file signs on Windows or Jira system
• Failing to synchronize if encountering attachment in issue that was removed in Jira server but link was still present
• Failing to synchronize if encountering attachment with 0 size on Azure DevOps side
• Missing users that are not in Windows Live ID domain in Azure DevOps
• Failing for sync few field types and if default on Azure DevOps side is set to null

Bugfixes:

• Numeric fields synchronization fixed
• Problem with error handling on saving new items in Azure Devops when using comments/history instead of custom fields

Bugfixes:

• Numeric fields synchronization fixed
• Problem with error handling on saving new items in Azure Devops when using comments/history instead of custom fields

Bugfixes:

• Empty date field synchronization throws an error

Bugfixes:

• Empty date field synchronization throws an error

Support for new REST API of Azure DevOps

Support for new REST API of Azure DevOps

• TFS4JIRA check-ins doesn't support the new Azure DevOps URL
• value mappings for user fields cannot display more than 1000 users in Jira Cloud
• Too many projects added in TFS check-ins configuration will lead to 400 error
• Pre-defined cache refresh time

• TFS4JIRA check-ins doesn't support the new Azure DevOps URL
• value mappings for user fields cannot display more than 1000 users in Jira Cloud
• Too many projects added in TFS check-ins configuration will lead to 400 error
• Pre-defined cache refresh time

Compatibility with Jira Server version 6.2 and newer

Compatibility with Jira Server version 6.2 and newer

Fixed bugs:

• TFS-2274 - Resolution field in Jira cannot be synced
• TFS-2146 - TFS4JIRA does not sync all attachments if one of them fails to get uploaded
• TFS-2144 - Link swapping doesn't work properly, and TFS4JIRA will automatically change the link type in a wrong way
• TFS-2105 - TFS4JIRA Synchronizer cannot sync JSD customer user account (user field) by copy value in a meaningful way
• TFS-2032 - Copy full TFS tree path mode does not copy the value when the TreePath field is set to the root of the tree path
• TFS-1067 - Gated check-ins

Fixed bugs:

• TFS-2274 - Resolution field in Jira cannot be synced
• TFS-2146 - TFS4JIRA does not sync all attachments if one of them fails to get uploaded
• TFS-2144 - Link swapping doesn't work properly, and TFS4JIRA will automatically change the link type in a wrong way
• TFS-2105 - TFS4JIRA Synchronizer cannot sync JSD customer user account (user field) by copy value in a meaningful way
• TFS-2032 - Copy full TFS tree path mode does not copy the value when the TreePath field is set to the root of the tree path
• TFS-1067 - Gated check-ins

Fixed bugs:

• TFS-2071 - Synchronizer ERROR: TF237079: Team Foundation could not update the work item because it was already updated by another use
• TFS-1984 - Git repos connection doesn't work if the user is using new Azure DevOps URL

Fixed bugs:

• TFS-2071 - Synchronizer ERROR: TF237079: Team Foundation could not update the work item because it was already updated by another use
• TFS-1984 - Git repos connection doesn't work if the user is using new Azure DevOps URL

Fixed bugs:

• Users Mapping Configuration is not carried over when cloning a SyncProfile
• Sub-task synchronization tried to create parent in Jira when its type is not mapped
• Initial synchronization failed for issues that have the Sprint field mapped

Fixed bugs:

• Users Mapping Configuration is not carried over when cloning a SyncProfile
• Sub-task synchronization tried to create parent in Jira when its type is not mapped
• Initial synchronization failed for issues that have the Sprint field mapped

• Compatibility with Jira Cloud API changes related to GDPR (usernames and user keys removal)
• New way of mapping users (map users once for whole profile)

• Compatibility with Jira Cloud API changes related to GDPR (usernames and user keys removal)
• New way of mapping users (map users once for whole profile)

• Possibility to show Check-ins panel only in selected projects on Jira Server.
• Possibility to map Jira user field to AzureDevOps single line text field.
• Small bugs fixes.
• Interface changes.

• Possibility to show Check-ins panel only in selected projects on Jira Server.
• Possibility to map Jira user field to AzureDevOps single line text field.
• Small bugs fixes.
• Interface changes.

• Possibility to hide Check-ins panel for selected projects on Jira Cloud.
• Interface changes to improve user experience. Added support for Personal Access tokens and API tokens.
• As always - we squashed some nasty bugs as well.

• Possibility to hide Check-ins panel for selected projects on Jira Cloud.
• Interface changes to improve user experience. Added support for Personal Access tokens and API tokens.
• As always - we squashed some nasty bugs as well.

Improved support of API Tokens for Jira Cloud

Bug fixes:

• FIPS compatibility supported
• Fixed markup conversion for attachments links

Improved support of API Tokens for Jira Cloud

Bug fixes:

• FIPS compatibility supported
• Fixed markup conversion for attachments links

• Mail notifications for administrators about all problems encountered in TFS4JIRA - https://confluence.spartez.com/display/TFS4JIRA/Mail+Notifications
• Synchronization of sub-task's parent change.
• Check-ins rescan permission fix

• Mail notifications for administrators about all problems encountered in TFS4JIRA - https://confluence.spartez.com/display/TFS4JIRA/Mail+Notifications
• Synchronization of sub-task's parent change.
• Check-ins rescan permission fix

Fixed bugs:

• Changeset link was pointing to invalid url in VSTS
• Changeset fetching problem with multiple TFS instances synchronized with one Jira

Fixed bugs:

• Changeset link was pointing to invalid url in VSTS
• Changeset fetching problem with multiple TFS instances synchronized with one Jira

• Improved performance by pre-filtering issues and work items before starting the synchronization
• Fixed bug with wrong order of work item's transitions

• Improved performance by pre-filtering issues and work items before starting the synchronization
• Fixed bug with wrong order of work item's transitions

Several bugfixes and improvements

Several bugfixes and improvements

This release marks TFS4JIRA compatible with new Data Center offering.

TFS4JIRA 7.3 with Hierarchy synchronization is here!

• Full Jira hierarchy (Epics and subtasks) ↔ TFS/VSTS hierarchy synchronization - https://confluence.spartez.com/display/TFS4JIRA/Hierarchy+Synchronization

• Many-to-one field mappings

• Fixed bug which prevented from Initial Synchronization of new TFS work items

• Comments synchronization bug fixed.

TFS4JIRA 7.2 with Test Steps synchronization is here!

• TFS/VSTS Test Steps to Jira RichText field bi-directional synchronization : https://confluence.spartez.com/pages/viewpage.action?pageId=45843454

Additional features:

• Web links / Hyperlinks synchronization.
• Issue key in TFS work item is a link to this issue.

• Update to our EULA as the prior one was outdated. Our new EULA can be viewed here - https://spartez.com/eula23.
• Documentation of Spartez Privacy Policy - https://spartez.com/privacy.

If you have any Qs, kindly contact us at our customer portal or send us an email to support@spartez.com .

• Fixed a bug that prevents synchronization of issues and work items

• TFS HTML fields ↔ Jira markup fields synchronization - For precise, description, comments-type fields synchronization: https://confluence.spartez.com/display/TFS4JIRA/HTML+and+Jira+Markup+Conversion
• Some minor fixes:
  • Support for TLS 1.2
  • Check-ins performance improvements

• TFS work items↔Jira issues links synchronization.
• Jira issue links↔TFS/VSTS workitems parent-child links (AKA hierarchy links) synchronization.

Bugfixes release

• Daylight saving time fixes

A bugfix release.

• Fixes defaults mapping for unassigned users.

• Fixed bug in Jira check-ins panel for Internet Explorer browsers
• Fixed bug with NullReferenceException when Jira resolution field is disabled
• Improved performance for large Jira instances (10k+ users)
• Updated Synchronizer installers certificate

In version 6.1, we added -

• Significant performance increase for large number of check-ins scenarios
• First synchronisation profile health checks - for Jira and TFS/VSTS connections
• Possibility to deploy Synchronizer as an Azure Web App
• Several smaller bugfixes

• Check-ins panel performance boost.
• A default value for TFS Iteration Path bug fixed.
• Fixed problem finding work items when VSTS time zone is not set to UTC.
• Possibility to use a custom field, instead of work item history, for related issue key in VSTS.
• Jira user interfaces improvement.
• ....and some other minor bug fixes.

• TFS Boolean field support
• Several bugfixes

• Easier deployment process
• Check-ins in a new, separate, development panel
• Simple installer (no additional dependencies)
• New TFS fields available for synchronization (e.g. rank order)
• Synchronizer windows docker container for evaluators
• Several bugfixes

Jira Agile sprints API is going to change. This version of TFS4Jira should work properly with old and new API.

• Fixed time zone handling in dateTime fields.
• Fixed issues with domains on Checkins configuration screen.

• Support for every workitem type to jira subtasks synchronization
• Few minor bugfixes

• Customizable list separator for Multivalue controls
• and few minor bugfixes

TFS4Jira 5.2.4 comes with a few enhancements and several bug fixes. Specifically:

• Ability to create support package, which should further speed up resolving support issues
• Increased performance of TFS check-ins tab
• Improved performance of synchronization
• Added option to map resolution field in Jira to any other in TFS/VSTS

We have also additionally resolved a number of issues reported through our support channels.

If you feel like sharing your opinions on using TFS4Jira please send us an email to support@spartez.com. And if you like our product please do not hesitate to leave a review on Atlassian Marketplace.

Enjoy TFS4Jira 5.2.4!

TFS4Jira 5.2.3 comes with in-built product analytics. With this feature we are able to observe the anonymous statistics of product usage and draw the heat maps for product improvement areas. With all the data collected we will be able to devote the upcoming releases to targeted improvements in the product configuration and usage.

Mind that with this release we needed to change the EULA for the product. Please make sure to get to know the new EULA before updating the add-on in your deployments.

We have also resolved a number of issues reported through our support channels.

If you feel like sharing your opinions on using TFS4Jira please send us an email to support@spartez.com. And if you like our product please do not hesitate to leave a review on Atlassian Marketplace.

Enjoy TFS4Jira 5.2.3!

TFS4Jira 5.2.2 comes with a variety of enhancements and several bug fixes. Specifically:

• we have enhanced the in-product caching which has resulted in a huge performance improvement in case of sprint synchronisation between the products;
• the caching of resources was also optimised;
• we have improved the way how licensing is checked by the synchroniser;
• we have also corrected and updated our documentation in several places.

On top of that we resolved a number of bugs reported by our users. Thank you!

If you feel like sharing your opinions on using TFS4Jira please send us an email to support@spartez.com. And if you like our product please do not hesitate to leave a review on Atlassian Marketplace.

Enjoy TFS4Jira 5.2.2!

TFS4Jira 5.2 is a very important release which brings a number of highly requested improvements. Specifically:

• the commits are scanned in parts and most recent git changes are fetched first
• we added a feature to fetch repository names to select them from the list during profile configuration
• git scans are now performed by parallel threads
• we have improved, simplified and optimized the UI in several places
• we added an option to disable HTML to Jira wiki markup conversion for descriptions, and other rich text fields
• we have performed a massive code refactoring, removed older libraries and replaced them with modern solutions
• we have migrated the solution to .NET 4.5 and refreshed the installer package

We have also resolved numerous bugs.

If you feel like sharing your opinions on using TFS4Jira please send us an email to support@spartez.com. And if you like our product please do not hesitate to leave a review on Atlassian Marketplace.

Enjoy TFS4Jira 5.2!

• Fixed estimation synchronization bug when default time tracking unit was not set to minutes
• Fixed closed sprints synchronization
• Improved performance for loading TFS check-ins tab

Compatibility with Jira 7.1

Bugfix release. For full list of changes visit our bugtracker.

Bug fix release. See our release notes for details

This release allows using TFS4Jira synchronizer with Jira or TFS that uses SSL self-signed certificate.

Additionally, some bugs were fixed.

For full list of changes visit our bugtracker.

Updating to this version requires updating the synchronizer web application to version 5.1.1

What's new in this version:

• One-to-many mapping for TFS States and Jira Statuses (see details).
• Support for Area Path and Iteration Path in TFS (see details).
• Support for Sprint field in Jira.
• REST API for check-ins in TFS4Jira Synchronizer (see details).
• Bug fixes.

For full list of changes visit our bug tracker.

What's new in this version:

• Compatibility with Jira 7.
• Search box for "Rescan Changeset".
• Force resynchronization for all errors in TFS4Jira Synchronizer.
• Minor bug fixes.

For full list of changes visit our bug tracker.

In this version:

• support for Git repositories in TFS,
• redesign of the 'TFS Check-ins' tab,
• improvements of synchronization filters in TFS4Jira Synchronizer,
• bug fixes.

Visit our Jira for details.

• option to set empty value in mapping
• bugfixes

• Synchronization filters allowing to synchronize only subset of Jira issues/TFS work items
• Bug fixing

Added information that Synchronizer-based check-ins scanning is not supported for TFS 2008. TFS 2008 users have to use plugin-based check-ins scanning fallback.

Compatibility of legacy check-ins scanning mode with Jira 6.3.11 and newer

This version comes with many fixes and improvements, mainly:

• Jira Data Center compatibility
• New initial synchronization modes
• Various bug fixes

Complete list of changes can be found here.

For full list of fixed bugs see here

This major TFS4Jira release comes with many long-awaited features such as:

* Initial Jira issues & TFS work items synchronization

* Both-way subtasks synchronization

* Both-way comments synchronization

* Timetracking fields synchronization

Please note that new TFS4Jira Synchronizer (downloadable from Spartez website) must be updated along with Jira plugin in order for the changes to be available.

Plus many other bugfixes and improvements. See full on TFS4Jira bugtracker.

New version because of Atlassian's "Incompatibility bug"

...and one more bug fixed.

Minor bugfixes (see full list here)

• Full support for synchronization work items from Hosted TFS
• Option to store Jira issue keys in work items history
• Migration to Atlassian Marketplace licensing only
• Option to synchronize only in one direction
• Bug fixes and improvements (see list)
• End of support for Microsoft Windows Server 2008 R1 (due to Team Explorer 2012 dependency) - apply only to Synchronizer

• Jira 6 compatibility fixes
• New TFS4Jira Synchronizer installer
• New logo

• Bugfix: TFS4Jira Synchronizer: creating synchronization profile failed with TFS 2012
• Other bugfixes (see list)

• Values mapping for assignee <-> assigned to field mapping
• Bugfix: synchronizations were not performed after some idle time
• Bugfix: erronous handling of timezones if GMT offset not in round hours

New feature added: Jira issues and TFS work items synchronizations. 

TFS4Jira Synchronizer automatically detects changes made to Jira issues (i.e. field values modifications, states transitions, attachments additions) and mirrors them to linked TFS work items and vice versa.

See the movie to see TFS4Jira Synchronizer in action.

fixed authentication with domain name present

fixed authentication with domain name present

updated MS TFS java library

updated MS TFS java library

bug fixes