| Table of Contents |
|---|
...
View collection-level information for the selected collection. Lack of this permission usually manifests as error message when running TFS / 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" error on static files (*.js, *.css) when I navigate to the application site.
...
Not all of the values from TFS / 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 / VSTS values are on the list now.
I want to synchronize only JIRA Issues and TFS / 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.
To which field in TFS should I map JIRA Resolution field?
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 / VSTS that uses self-signed SSL certificate
...