Versions Compared

Key

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

Table of Contents


Licensing

...

  • View collection-level information for the selected collection. Lack of this permission usually manifests as error message when running TFS / Azure DevOps (formerly VSTS) connection test, although sometimes it's not the case (the test passes, but TFS quietly returns no results). How to set the permission:

    • Visual Studio 2010/2012: Team -> Team Project Collection Settings -> Security

  • Read permission for the selected folder. How to set the permission:
    • Visual Studio 2010: View -> Other Windows -> Source Control Explorer -> Right click on the folder -> Properties ->  Security
    • Visual Studio 2012: View -> Other Windows -> Source Control Explorer -> Right click on the folder -> Advanced -> Security

Also, please verify that your TFS4JIRA plugin version is 1.7.5 or newer as previous versions contained a critical bug.

TFS4JIRA Synchronizer installation

...

You need to run following command in console:  %windir%\system32\inetsrv\appcmd unlock config -section:system.webServer/modules


TFS4JIRA Synchronizer installer finished without any complaints but I get "HTTP 500.19" with 0x80070005 code error when I navigate to the application site.

This problem might be related to the permission of installation location. It might occur when you have a different physical path for your IIS site, and the user does not have full permission at the directory of that physical path. To solve this, please uninstall TFS4JIRA Synchronizer, then grant permission to the user for the directory. Afterwards, it should work after installation again.

TFS4JIRA Synchronizer installer finished without any complaints but I get "HTTP 500" error on static files (*.js, *.css) when I navigate to the application site.

...

Due to the Entity Framework bug, the pre 5.2 to 6.0.2 (or newer) upgrade requires two steps. First, you have to install Synchronizer version 6.0.0 (Web installerOffline installer), make sure it works and then upgrade to newest version.

...

Direct upgrade from version 5.1.x or older to version 6.0.2 or newer is not possible. You have to upgrade Synchronizer in two steps. First, uninstall your current version and install Synchronizer version 6.0.0 (Web installer, Offline installer), make sure it works and then upgrade to newest version.

...

Not all of the values from TFS / Azure DevOps (formerly VSTS) are visible on the mappings screen (for example only subset of State fields can be chosen).

Remove folder  <synchronizer_path>\App_Data\TFSClientCache  and check again if all of the TFS / Azure DevOps (formerly VSTS) values are on the list now.

I want to synchronize only Jira Issues and TFS / Azure DevOps (formerly VSTS) Work Items of some types and ignore other items.

...

After you do that, you need to restart the application pool that TFS4JIRA synchronizer uses (the pool name is "TFS4JIRA Sync App Pool") - you can do that in the IIS ManagerLearn more about azure devops integration with Jira.