SpecSync Documentation
Jira
Jira
  • Introduction to SpecSync for Jira
  • Getting started
    • Getting started using SpecFlow
    • Getting started using Cucumber or other Gherkin-based BDD tool
  • Installation & Setup
    • Install as .NET tool
    • Install as .NET Console App
    • Install as native binaries for Linux or macOS
    • Install as Docker image
    • Setup and Configure
  • Features
    • Push features
      • Pushing scenario changes to Test Cases
      • Configuring the format of the synchronized test cases
      • Synchronizing Scenario Outlines
      • Update Test Case fields
      • Attach files to Test Cases using tags
      • Customization: Setting Test Case fields with default values
      • Customization: Update custom Test Case fields on push
      • Customization: Ignoring marked Test Case steps
      • Customization: Ignoring Test Case Tags
      • Customization: Ignore non-supported local tags
      • Customization: Mapping tags
      • Customization: Synchronizing scenarios from feature branches
      • Customization: Automatically link changed Test Cases
      • Customization: Synchronize linked artifact titles
      • Customization: Do not synchronize title
    • Pull features
      • Pulling Test Case changes to local scenarios
    • Common synchronization features
      • Configuration key
      • Remote scope
      • Linking Work Items using tags
      • Synchronizing Test Case hierarchies
      • Excluding scenarios from synchronization
      • Synchronization conflict resolution
    • Test result publishing features
      • Publishing test result files
    • General features
      • Jira authentication options
      • Configuration file
      • Hierarchical configuration files
      • Local test case conditions
      • Configuration wizards
      • SpecSync plugins
    • Customizations
    • Plugin list
  • Licensing
  • Guides
    • What is my Jira server URL?
    • Jira Test Case Management (TCM) solution
    • How to define the local feature-set to be synchronized
    • Filters and scopes
    • How to use SpecSync from build or release pipeline
    • How to upgrade to a newer version of SpecSync
    • How to attach files to test results
    • Using SpecSync with Cucumber
    • Using SpecSync with Cypress
    • Using SpecSync with Postman
    • Using SpecSync with TestNG
    • Using SpecSync on macOS or Linux
    • Using SpecSync inside a Docker container
    • Migrating from SpecSync v1 to v5
  • Changelog
  • Release Model and Roadmap
  • Downloads
  • Reference
    • Command line reference
      • init
      • upgrade
      • push
      • pull
      • publish-test-results
      • version
    • Configuration reference
      • toolSettings
      • local
      • remote
      • jira
      • knownRemotes
      • synchronization
        • push
        • pull
        • links
        • attachments
        • format
        • fieldUpdates
      • hierarchies
      • publishTestResults
      • specFlow
      • customizations
    • Compatibility
    • Older versions
  • Contact
    • SpecSync Support
    • Troubleshooting
    • FAQ
  • Project Website
Powered by GitBook
On this page

Was this helpful?

  1. Reference
  2. Configuration reference

remote

PreviouslocalNextjira

Last updated 1 year ago

Was this helpful?

This configuration section contains settings for accessing the test cases on the remote Jira server.

The following example shows the most common options within this section.

{
  ...
  "remote": {
    "serverUrl": "https://specsyncdemo.atlassian.net/",
    "project": "MyCalculator",
    "user": "myuser",
    "password": "%MYPWD%",
  },
  ...
}

Settings

The remote settings of the Jira project can also be specified in the knownRemotes section of one of the parent configuration file or in the user-specific configuration file. Check for details.

Setting
Description
Default

serverUrl

The base URL of the Jira server. E.g. https://yourcompany.atlassian.net/, http://myjiraserver:9090/

mandatory

project

The Jira project key that you can see in the URL when you access the project, e.g. PRJ01

mandatory

authenticationMethod

The authentication method to be used for connecting to the remote server. Possible values: Interactive, UserNamePassword, PAT

automatically detect UserNamePassword or PAT

user

interactive prompt

password

interactive prompt

securityProtocol

The security protocol to be used for the remote connection (Ssl3, Tls, Tls11, Tls12).

system default

ignoreCertificateErrorsForThumbprint

SSL is verified by the OS

The Jira user name or (PAT) to be used for authentication. It may contain environment variables in ...{env:ENV_VAR}... form. See for details.

The password to be used for authentication. It may contain environment variables in ...{env:ENV_VAR}... form. See for details.

The thumbprint of the server certificate that should be treated as trusted. It is recommended to install trusted certificates on the operating system instead of using this setting. See related for details.

The ignoreCertificateErrorsForThumbprint setting is planned for a future version of SpecSync for Jira. Please check the for details.

Hierarchical configuration files
Roadmap
Configuration reference
personal access token
Jira authentication options
Jira authentication options
Troubleshooting entry