Child pages
  • Required network configuration

Versions Compared

Key

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

...

Below you'll find detailed information for each Jira and TFS server /Azure DevOps supported variants:

Table of Contents
maxLevel1

...

Gliffy Diagram
chromemin
namenetwork_legend
pagePin2

Jira Server

...

+ TFS

...

/ Azure DevOps Server

Gliffy Diagram
chromemin
size600
namenetwork_jira_server_onpremises_tfs
pagePin19

Jira Server

...

+ Azure DevOps

...

Services

Gliffy Diagram
chromemin
size600
namenetwork_jira_server_microsoft_hosted_tfs
pagePin8

Anchor
jiracloud
jiracloud

Jira Cloud + TFS

...

/ Azure DevOps Server

Note: In this configuration our TFS4JIRA OnDemand checkins component hosted on tfs4jira-ondemand-checkins.spartez.com connects (red line) to your TFS4JIRA Synchronizer application using HTTP/HTTPS calls. You should configure your firewall in such a way that the web interface of your Synchronizer application will be reachable from tfs4jira-ondemand-checkins.spartez.com. In most cases it means you should open port 80 (for HTTP) or 443 (for HTTPS) for incoming connections from tfs4jira-ondemand-checkins.spartez.com (18.195.184.68), but the port may vary depending on your configuration.

...

Gliffy Diagram
chromemin
size600
namenetwork_jira_cloud_onpremises_tfs
pagePin7

Jira Cloud + Azure DevOps

...

Services

Note: In this configuration our TFS4JIRA on-demand checkins component hosted on tfs4jira-ondemand-checkins.spartez.com connects(red line) to your TFS4JIRA Synchronizer application using HTTP/HTTPS calls. You should configure your firewall in such a way that the web interface of your Synchronizer application will be reachable from tfs4jira-ondemand-checkins.spartez.com. In most cases it means you should open port 80 (for HTTP) or 443 (for HTTPS) for incoming connections from tfs4jira-ondemand-checkins.spartez.com (18.195.184.68), but the port may vary depending on your configuration.

...