| Table of Contents |
|---|
Licensing
...
Please refer to Atlassian documentation: https://www.atlassian.com/licensing/purchase-licensing
TFS / Azure DevOps (formerly VSTS) check-ins synchronization (TFS4JIRA Jira Plugin)
I don't have "TFS Check-ins" tab at all on issue view
...
Please check if permissions for project in TFS are correct for account that you provided. As a test you can check if this option works correctly for admin account.
I've defined a TFS / Azure DevOps (formerly VSTS) repository in TFS4JIRA Synchronizer but I can't see any check-ins.
First thing to check is whether TF4Jira managed to successfully scan your TFS / Azure DevOps (formerly VSTS) repository. Navigate to tab Check-ins Scanning and click on Edit link – you should see information about last repository scan. Please verify if Last Scan Time is OK and if Last Scanned Revision number matches the most recent revision number in your repository. In case of last synchronization attempt failure, you should see also error details presented. You can also click on Edit link and then press Test button to check if repository data you've provided are OK. Below you will find a list of the most common errors you may encounter.
...
Most common cause of such an error is either invalid TFS / Azure DevOps (formerly VSTS) server URL or invalid project collection name. Regarding URL please verify that you've provided full URL with proper scheme (http:// vs. https://), port number and path component (by default, local TFS / Azure DevOps (formerly VSTS) installation URL ends with /tfs, e.g. http://example.com/tfs).
...
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.
...
There is a bug in Jira 6.0.1 that prevents Synchronizer to check the date set in Jira instance. When you have Jira 6.0.1 you need to have same timezone set in Jira and in the computer on which Synchronizer is installed.
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.
You should go to page "Jira Issue Type/TFS Work Item Type" and select "Do nothing" option instead of "Raise error" in value mappings section.
...
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: http://blogs.msdn.com/b/teams_wit_tools/archive/2009/03/31/work-item-rules-workaround-saving-the-resolved-reason.aspx
Miscellaneous
Connecting the synchronizer with Jira or TFS / Azure DevOps (formerly VSTS) that uses self-signed SSL certificate
In order to succesfully connect to a machine that uses self-signed certificate, you will need to add the following entry to the synchronizer's <synchronizer_path>\Web.config file (required changes are in bold):
...