| Table of Contents |
|---|
Licensing
...
If your license key is being rejected, most probably it's because you are trying to enter your key in the wrong place. See this page for more detailed information on providing a license key. Please remember that from version 2.1.0 TFS4JIRA accepts only Atlassian Marketplace licenses. If you have old license type, obtained directly from SpartezAppfire, please write to sales@spartezto support@appfire.com in order to have your license migrated.
...
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.
...
TFS4JIRA Synchronizer installer finished without any complaints but I get "HTTP 503" error when I navigate to the application site.
(This answer is not valid for Synchronizer 9.0+ versions - Synchronzier changed to 64-bit.) This problem can occur when 32-bit web applications are not enabled in IIS configuration - please refer to this solution: http://manasbhardwaj.net/running-32-bit-web-application-iis-8
...
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 installer, Offline 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.
...
The problem with mapping Jira Resolution field to TFS Reason field is that Jira only allows modifying the Resolution field during state transitions that mark issues as Resolved. Meanwhile, in TFS, the Reason field is updated during every transition, and the value it contains heavily depend on the state that the work item is being transitioned to. And that breaks syncing with Jira, because changes in the Resolution field are not always allowed in Jira. The Resolved Reason field was introduced in TFS in order to serve the same purpose as Resolution in Jira - it is only set (automatically by TFS) when work item is being resolved. The complication here is that the Resolved Reason field is not necessarily available in all TFS project schemes. However, it can be added to any scheme. The process of adding Resolved Reason field to your TFS and setting it up so that it updates when expected is described here: httphttps://blogsdocs.msdnmicrosoft.com/b/teams_wit_tools/archive/2009/03/31/work-item-rules-workaround-saving-the-resolved-reason.aspxen-us/azure/devops/reference/xml/change-workflow-wit?view=azure-devops
Miscellaneous
Connecting the synchronizer with Jira or TFS / Azure DevOps (formerly VSTS) that uses self-signed SSL certificate
...