Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Below you will find TFS4JIRA compatibility matrix.

...

  • Operating System: Windows Server 2008 R2 SP1 or Windows 7 SP1 or newer
  • CPU:  x86-64 or x86 architecture CPU

Please note that 6.0 uses several Microsoft Prerequisites that will be installed/enabled during synchronizer installation. 

...

  • Operating System: Windows Server 2008 R2 SP1 or Windows 7 SP1 or newer
  • CPU:  x86-64 or x86 architecture CPU
  • With IIS windows feature version 7.0 or newer with ASP.NET 4.5 enabled -  it should be enabled in Programs in Control Panel. (see screenshot bellow)
  • TFS 2012 Update 4 Object Model (used to connect to the Team Foundation Servers; works for all versions of TFS including TFS 2010-2015 and VSTS).
  • .NET Framework 4.5 or newer

Please remember that IIS Express version won't work with Synchronizer.

Version 5.0 - 5.2.1

TFS4JIRA Synchronizer web app must be installed on: 

  • Operating System: Windows Server 2008 R2 SP1 or Windows 7 SP1 or newer
  • CPU:  x86-64 or x86 architecture CPU
  • With IIS windows feature version 7.0 or newer with ASP.NET 4.5 enabled -  it should be enabled in Programs in Control Panel. (see screenshot bellow)
  • Please remember that IIS Express version won't work with Synchronizer.
  • TFS 2012 Update 4 Object Model (used to connect to the Team Foundation Servers; works for all versions of TFS including TFS 2010-2015 and VSTS).
  • .NET Framework 4.5 or newer
  • SQL Server Compact Edition 4.0 (required even when full SQL Server version is installed)

 Image Modified

Anchor
components
components
TFS4JIRA Synchronizer 6.0 will install/enable the following components :

TFS4JIRA Synchronizer 7.1 will install/enable the following components :


Note
titleDo not configure the synchronizer to use MS SQL Server

While it is technically possible to use the synchronizer's configuration files to connect to a different database than SQL Server Compact (for example to MS SQL Server), such a configuration is not tested and not supported. If you do reconfigure the synchronizer this way, it might work, but in case of problems, you are on your own

...