Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Changed SS-macros to images

...

In order to define a TFS repository connection in JIRA, you need to navigate to Administration -> Add-ons -> TFS4JIRA Configuration  and click link shown on the screenshot below.

Image Added

On screen Team Foundation Server Repositiories click link Add TFS repository.

Image Added

 

After clicking Add TFS repository link a popup will apear, where you can enter TFS repository parameters.

Image Added

 

Common Repository Parameters

...

You need to provide credentials of a user account that has at least read access to the TFS server that you are configuring

  • User Name

  • Domain

  • Password

TFS 2010, 2012, Hosted - specific Parameters

TFS 2010 and TFS 2012 supports the notion of "Project Collections". If you set the server version to "TFS 2010" or "TFS2012", you can specify the project collection to use when querying the repository. If left blank, the default colection (called DefaultCollection) is used.

Image Added

TFS 2008 - specific Parameters

TFS 2008 does not include an out-of-the-box web access capability. This means that viewing files and changesets, as well as their history and diffs, require installation of a free TFS Web Access service. This service provides web access to TFS and exposes an URL, which has to be specified in the TFS Web Access URL parameter. If this parameter is left blank, there will be no links to file views, history and diffs in changeset views in issue panels.

 

Testing Server Connection

In order to test if the URL of your TFS repository and your credentials are correct, click the Test button. This will cause TFS4JIRA to perform a test connection to the TFS server. In case of errors, a dialog listing the cause of the problem will be displayed.

...

  • Status – for viewing repository scanning status

  • Edit – for editing repository parameters

  • Delete – for removing repository information from JIRA

  • Clear – for clearing cached repository information from JIRA. This causes the repository to get rescanned and reindexed, which is useful in case a check-in comment or other changeset metadata gets edited

Image Added